File mingw64-libjpeg-turbo.changes of Package mingw64-libjpeg-turbo

Overview Repositories Revisions Requests Users Attributes Meta

File mingw64-libjpeg-turbo.changes of Package mingw64-libjpeg-turbo (Revision b37101961960129cfe3454b885bcef42)

Currently displaying revision b37101961960129cfe3454b885bcef42 , Show latest

-------------------------------------------------------------------
Thu Feb 15 20:59:24 UTC 2024 - Ralf Habacker <ralf.habacker@freenet.de>

- Removed providing of mingw64-libjpeg-devel to fix the
  mingw64-imagemagick build issue, that incorrectly selects this
  package. The use of this package can be selected by using
  mingw64-libjpeg8-devel.

-------------------------------------------------------------------
Mon Feb  5 19:25:12 UTC 2024 - Martin Hauke <mardnh@gmx.de>

- Update URL
- Update Source URL: sf.net -> github.com
- Update to version 3.0.2
  * Fixed a signed integer overflow in the tj3CompressFromYUV8(),
    tj3DecodeYUV8(), tj3DecompressToYUV8(), and tj3EncodeYUV8()
    functions, detected by the Clang and GCC undefined behavior
    sanitizers, that could be triggered by setting the align
    parameter to an unreasonably large value. This issue did not
    pose a security threat, but removing the warning made it
    easier to detect actual security issues, should they arise in
    the future.
  * Introduced a new parameter (TJPARAM_MAXMEMORY in the
    TurboJPEG C API and TJ.PARAM_MAXMEMORY in the TurboJPEG Java
    API) and a corresponding TJBench option (-maxmemory) for
    specifying the maximum amount of memory (in megabytes) that
    will be allocated for intermediate buffers, which are used
    with progressive JPEG compression and decompression, optimized
    baseline entropy coding, lossless JPEG compression, and
    lossless transformation. The new parameter and option serve
    the same purpose as the max_memory_to_use field in the
    jpeg_memory_mgr struct in the libjpeg API, the JPEGMEM
    environment variable, and the cjpeg/djpeg/jpegtran -maxmemory
    option.
  * Introduced a new parameter (TJPARAM_MAXPIXELS in the TurboJPEG
    C API and TJ.PARAM_MAXPIXELS in the TurboJPEG Java API) and a
    corresponding TJBench option (-maxpixels) for specifying the
    maximum number of pixels that the decompression, lossless
    transformation, and packed-pixel image loading
    functions/methods will process.
  * Fixed an error ("Unsupported color conversion request") that
    occurred when attempting to decompress a 3-component lossless
    JPEG image without an Adobe APP14 marker. The decompressor
    now assumes that a 3-component lossless JPEG image without an
    Adobe APP14 marker uses the RGB colorspace if its component
    IDs are 1, 2, and 3.
- Update to version 3.0.1
  * The x86-64 SIMD functions now use a standard stack frame,
    prologue, and epilogue so that debuggers and profilers can
    reliably capture backtraces from within the functions.
  * Fixed two minor issues in the interblock smoothing algorithm
    that caused mathematical (but not necessarily perceptible)
    edge block errors when decompressing progressive JPEG images
    exactly two MCU blocks in width or that use vertical
    chrominance subsampling.
  * The TurboJPEG API now supports 4:4:1 (transposed 4:1:1)
    chrominance subsampling, which allows losslessly transposed or
    rotated 4:1:1 JPEG images to be losslessly cropped, partially
    decompressed, or decompressed to planar YUV images.
  * Fixed various segfaults and buffer overruns (CVE-2023-2804)
  * that occurred when attempting to decompress various
    specially-crafted malformed 12-bit-per-component and
    16-bit-per-component lossless JPEG images using color
    quantization or merged chroma upsampling/color conversion.  The
    underlying cause of these issues was that the color
    quantization and merged chroma upsampling/color conversion
    algorithms were not designed with lossless decompression
    in mind.  Since libjpeg-turbo explicitly does not support color
    conversion when compressing or decompressing lossless JPEG
    images, merged chroma upsampling/color conversion never should
    have been enabled for such images.  Color quantization is a
    legacy feature that serves little or no purpose with lossless
    JPEG images, so it is also now disabled when decompressing such
    images.  (As a result, djpeg can no longer decompress a
    lossless JPEG image into a GIF image.)
  * Fixed an oversight in 1.4 beta1[8] that caused various
    segfaults and buffer overruns when attempting to decompress
    various specially-crafted malformed 12-bit-per-component JPEG
    images using djpeg with both color quantization and RGB565
    color conversion enabled.
  * Fixed an issue whereby `jpeg_crop_scanline()` sometimes
    miscalculated the downsampled width for components with 4x2 or
    2x4 subsampling factors if decompression scaling was enabled.
    This caused the components to be upsampled incompletely, which
    caused the color converter to read from uninitialized memory.
    With 12-bit data precision, this caused a buffer overrun or
    underrun and subsequent segfault if the sample value read from
    uninitialized memory was outside of the valid sample range.
  * Fixed a long-standing issue whereby the `tj3Transform()`
    function, when used with the `TJXOP_TRANSPOSE`,
    `TJXOP_TRANSVERSE`, `TJXOP_ROT90`, or `TJXOP_ROT270` transform
    operation and without automatic JPEG destination buffer
    (re)allocation or lossless cropping, computed the worst-case
    transformed JPEG image size based on the source image
    dimensions rather than the transformed image dimensions.  If a
    calling program allocated the JPEG destination buffer based on
    the transformed image dimensions, as the API documentation
    instructs, and attempted to transform a specially-crafted
    4:2:2, 4:4:0, 4:1:1, or 4:4:1 JPEG source image containing a
    large amount of metadata, the issue caused `tj3Transform()` to
    overflow the JPEG destination buffer rather than fail
    gracefully.  The issue could be worked around by setting
    `TJXOPT_COPYNONE`.  Note that, irrespective of this issue,
    `tj3Transform()` cannot reliably transform JPEG source images
    that contain a large amount of metadata unless automatic JPEG
    destination buffer (re)allocation is used or `TJXOPT_COPYNONE`
    is set.
  * Significantly sped up the computation of optimal Huffman
    tables. This speeds up the compression of tiny images by as
    much as 2x and provides a noticeable speedup for images as
    large as 256x256 when using optimal Huffman tables.
  * All deprecated fields, constructors, and methods in the
    TurboJPEG Java API have been removed.
  * Arithmetic entropy coding is now supported with
    12-bit-per-component JPEG images.
  * Overhauled the TurboJPEG API to address long-standing
    limitations and to make the API more extensible and intuitive.

-------------------------------------------------------------------
Thu Jun 15 11:28:18 UTC 2023 - Martin Hauke <mardnh@gmx.de>

- Update to version 2.1.5.1
  * lots of changes since 1.4.0
  * use cmake instead of autotools for building
  * drop not longer needed patches:
    + jpeg-typedef-boolean.diff
    + libjpeg-1.4.0-ocloexec.patch
    + libjpeg-turbo-1.4.0-int32.patch
    + libjpeg-turbo-remove-test.patch

Places

File mingw64-libjpeg-turbo.changes of Package mingw64-libjpeg-turbo (Revision b37101961960129cfe3454b885bcef42)

Places