This is really a pretty minor update, but I wanted to get in the fix reported here (https://hydrogenaud.io/index.php?topic=118619.msg979396#msg979396) where garbage characters could get appended to imported ID3v2 TXXX tags (thanks Nejiro). This mostly applies to DSF files, but the ID3v2 import can now be used with other file types as well.
Since the integration with OSS-Fuzz there have been four issues discovered and fixed, plus many more discovered locally and fixed (using libFuzzer and various Clang sanitizers). None of these were exploitable and so I don't consider them at all critical, but they are worth getting.
Changes:- fixed: OSS-Fuzz issues 19925, 19928, 20060, 20448
- fixed: trailing garbage characters on imported ID3v2 TXXX tags
- fixed: various minor undefined behavior and memory access issues
- fixed: sanitize tag extraction names for length and path inclusion
- improved: reformat wvunpack "help" and split into long + short versions
- added: regression testing to Travis CI for OSS-Fuzz crashers
As always, the sources and binaries are available on GitHub (https://github.com/dbry/WavPack/releases/tag/5.3.0) and (somewhat less securely) on my download page (http://www.wavpack.com/downloads.html).
Thanks, and stay safe everyone! :)
Thank you for your continued work on this excellent codec. WavPack has been my primary lossless codec for a very long time now. Thank you, again!
Thnx for the new release :)
Many, many thanks. Keep the good work.
Hi Bryant, I just installed Ubuntu 20.04 lts and in the repositories there is wavpack version 5.2.0-1, how do I go to 5.3.0? Or if there are no changes can I also keep these that are here?
Thanks
Thanks.
Hi Bryant, I just installed Ubuntu 20.04 lts and in the repositories there is wavpack version 5.2.0-1, how do I go to 5.3.0? Or if there are no changes can I also keep these that are here?
Thanks
Hi Nejiro. You definitely
do not want version 5.2.0 because that's the version that has the bug you discovered. :)
I would suggest either continuing to use the 5.2.1 that I built and attached to the other thread, or use the 5.3.0 binaries that I am attaching here.
edit: deleted binaries with libcrypto1.0.0 dependency.
In fact I saw that it has that bug, with binaries I can't do anything about it, I remember that I had done a procedure to update but I don't remember how to do it, it seems to me that I had put files on a system folder ..... .
Thanks
Ok, I went to read the other tread and I put these files https://hydrogenaud.io/index.php?action=dlattach;topic=118619.0;attach=16269 in / usr / local / bin so I can have this version 5.3.0 what's different?
Thanks
It no longer works if I put those files on / usr / local / bin, this error comes out
"wavpack -hmv --import-id3 *.dsf
wavpack: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
"
Thanks
So, I confirm that if I put the binaries that you have released, both those of the other tread and those of 5.3.0 on / usr / local / bin the program does not work, so I must necessarily use those of the repositories of 20.04 that have the bug ...... I can use it the same is not a problem, but in 18.04 it worked, here not ......
Sorry, I guess libcrypto1.0.0 is not standard anymore.
I have created a new set of binaries without that dependency. Good luck!
I always have to put them on / usr / local / bin right?
These are fine ....
Thank you very much
Great! :)
Thanks a bunch, David, your work and superb CODEC very much appreciated.
Thanks, bryant!
Thanks David, for such a solid, ever-up-to-date lossless/lossy format!
Nilson