public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libexif: Update to version 0.6.24
Date: Tue, 27 Dec 2022 16:15:49 +0000	[thread overview]
Message-ID: <6f4a70fa-5e05-69d6-bdc9-41d53f8bf89f@ipfire.org> (raw)
In-Reply-To: <20221227120002.12161-6-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3759 bytes --]

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> - Update from version 0.6.22 to 0.6.24
> - Update of rootfile not required
> - source file no longer provided in xz format - changed to bz2
> - Changelog (Two CVE's fixed in 0.6.23)
>     libexif-0.6.24 (2021-11-25):
> 	   * Translation updates: sr, vi, pl, uk, french
> 	   * fixed regression in exif_data_load_data which could not load EXIF in JPEG data anymore
> 	   * Decode lots of Canon tag names
> 	   * removed empty strings from translation (empty string would translate to the PO info header)
> 	   * various warning removals and code improvements
> 	   * added sample "persistent" afl fuzzer (100x faster than normal afl fuzzer)
>     libexif-0.6.23 (2021-09-12):
> 	  * Translation updates: es, pl, uk, fr
> 	  * EXIF_TAG_SENSITIVITY_TYPE decoder added, added some more Exif 2.3 tags:
> 	    - EXIF_TAG_STANDARD_OUTPUT_SENSITIVITY
> 	    - EXIF_TAG_RECOMMENDED_EXPOSURE_INDEX
> 	    - EXIF_TAG_ISO_SPEED
> 	    - EXIF_TAG_ISO_SPEEDLatitudeYYY
> 	    - EXIF_TAG_ISO_SPEEDLatitudeZZZ
> 	    - EXIF_TAG_OFFSET_TIME
> 	    - EXIF_TAG_OFFSET_TIME_ORIGINAL
> 	    - EXIF_TAG_OFFSET_TIME_DIGITIZED
> 	    - EXIF_TAG_IMAGE_DEPTH
> 	  * be more relaxed to out of order JPG / EXIF dataheaders in files generated by some tools
> 	  * default GPS IFD table added
> 	  * Decode more Nikon Makernote tag names
> 	  * Added Apple iOS Makernote
> 	  * Security fixes:
> 	    * CVE-2020-0198: unsigned integer overflow in exif_data_load_data_content
> 	    * CVE-2020-0452: compiler optimization could remove an a
> 	      bufferoverflow check, making a buffer overflow possible with some
> 	      EXIF tags
> 	    * some more denial of service (compute time or stack exhaustion) counter-measures
> 	      added that avoid minutes of decoding time with malformed files found
> 	      by OSS-Fuzz
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>  lfs/libexif | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/lfs/libexif b/lfs/libexif
> index c23dfd573..c89232b1c 100644
> --- a/lfs/libexif
> +++ b/lfs/libexif
> @@ -1,7 +1,7 @@
>  ###############################################################################
>  #                                                                             #
>  # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2018  IPFire Team  <info(a)ipfire.org>                     #
> +# Copyright (C) 2007-2022  IPFire Team  <info(a)ipfire.org>                     #
>  #                                                                             #
>  # This program is free software: you can redistribute it and/or modify        #
>  # it under the terms of the GNU General Public License as published by        #
> @@ -26,15 +26,15 @@ include Config
>  
>  SUMMARY    = An EXIF Tag Parsing Library for Digital Cameras
>  
> -VER        = 0.6.22
> +VER        = 0.6.24
>  
>  THISAPP    = libexif-$(VER)
> -DL_FILE    = $(THISAPP).tar.xz
> +DL_FILE    = $(THISAPP).tar.bz2
>  DL_FROM    = $(URL_IPFIRE)
>  DIR_APP    = $(DIR_SRC)/$(THISAPP)
>  TARGET     = $(DIR_INFO)/$(THISAPP)
>  PROG       = libexif
> -PAK_VER    = 2
> +PAK_VER    = 3
>  
>  DEPS       =
>  
> @@ -48,7 +48,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_BLAKE2 = 3771dcf2d6a9d9a63e2d3fcdd49487bec7af45d1d18aef1bf3d427893b0cfc464fab37adfbfa549571a58540c7c1eb402724afe05c36baa51a6b7f19ee17ed2b
> +$(DL_FILE)_BLAKE2 = 75d3a2b4fefd7b7706226e70d31250ef7e99eeb81a4839ddc36cc9e3180534542d8a02851f8e6fd5034bbc925a616ead8c4bfb0cce8bc5886c3ec54811914a6b
>  
>  install : $(TARGET)
>  

  reply	other threads:[~2022-12-27 16:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 11:59 [PATCH] curl: Update to version 7.87.0 Adolf Belka
2022-12-27 11:59 ` [PATCH] harfbuzz: Update to version 6.0.0 Adolf Belka
2022-12-29 11:21   ` Peter Müller
2022-12-27 11:59 ` [PATCH] libcap: Update to version 2.66 Adolf Belka
2022-12-29 11:20   ` Peter Müller
2022-12-27 11:59 ` [PATCH] libcdada: Update to version 0.4.0 Adolf Belka
2022-12-29 11:19   ` Peter Müller
2022-12-27 11:59 ` [PATCH] libconfig: Update to version 1.7.3 Adolf Belka
2022-12-27 11:59 ` [PATCH] libexif: Update to version 0.6.24 Adolf Belka
2022-12-27 16:15   ` Peter Müller [this message]
2022-12-27 11:59 ` [PATCH] libffi: Update to version 3.4.4 Adolf Belka
2022-12-27 16:13   ` Peter Müller
2022-12-27 11:59 ` [PATCH] libgpg-error: Update to version 1.46 Adolf Belka
2022-12-29 11:19   ` Peter Müller
2022-12-27 12:00 ` [PATCH] libidn: Update to version 1.41 Adolf Belka
2022-12-27 16:17   ` Peter Müller
2022-12-27 12:00 ` [PATCH] libinih: Update to version r56 Adolf Belka
2022-12-27 16:16   ` Peter Müller
2022-12-27 12:00 ` [PATCH] libjpeg: Update to version 2.1.4 Adolf Belka
2022-12-27 16:12   ` Peter Müller
2022-12-29 11:21 ` [PATCH] curl: Update to version 7.87.0 Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6f4a70fa-5e05-69d6-bdc9-41d53f8bf89f@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox