Binaries and source tarball are here:
https://sourceforge.net/projects/libjpeg-turbo/files/2.1.0/
Change log is here:
https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/2.1.0
In addition to the items mentioned in the change log, libjpeg-turbo is
also now completely integrated with OSS-Fuzz, Google's continuous
fuzzing engine. Google sponsored my labor to perform this integration,
which improved fuzzing code coverage for libjpeg-turbo by about 3x. All
code paths that accept arbitrary image files are now covered, and the
only code remaining uncovered is code that implements infrequently-used
features of the libjpeg API (refer to
https://github.com/libjpeg-turbo/libjpeg-turbo/issues/516.) This effort
has already uncovered a handful of innocuous issues reported by MSan and
UBSan, all of which have been fixed in this release. Going forward,
OSS-Fuzz will make it easier to catch potential security issues in new
code before those issues are released, which will improve the quality of
libjpeg-turbo as well as reduce the maintenance burden on me.
I also want to mention a long-term feature proposal that is currently in
need of funding:
https://github.com/libjpeg-turbo/libjpeg-turbo/issues/517
This proposal would overhaul the TurboJPEG API to make it as versatile
as the libjpeg API (or at least nearly so) as well as generally less
clunky, in hopes of giving developers a viable path forward from the
30-year-old libjpeg API. If your organization is interested in
sponsoring this effort, then please contact me off-list.
DRC
--
You received this message because you are subscribed to the Google Groups
"libjpeg-turbo Announcements" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/libjpeg-turbo-announce/cffef863-3fe9-5fb4-7c9c-7cd26003efda%40virtualgl.org.
