From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libavif: security bump to version 1.1.1
Date: Mon, 5 Aug 2024 15:48:56 +0200 [thread overview]
Message-ID: <20240805154856.41f06fb1@windsurf> (raw)
In-Reply-To: <20240805115224.3473431-1-aperez@igalia.com>
Hello Adrian,
On Mon, 5 Aug 2024 14:52:22 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:
> The release notes for version 1.1.0 mention fixes for memory handling
> issues and bugs found out by fuzzing, which is the reason why this may
> be considered a security update, despite them not having CVEs assigned:
>
> https://github.com/AOMediaCodec/libavif/releases/tag/v1.1.0
> https://github.com/AOMediaCodec/libavif/releases/tag/v1.1.1
>
> Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> ---
> package/libavif/libavif.hash | 2 +-
> package/libavif/libavif.mk | 9 +++++----
> 2 files changed, 6 insertions(+), 5 deletions(-)
This update breaks legal-info:
ERROR: while checking hashes from package/libavif/libavif.hash
ERROR: LICENSE has wrong sha256 hash:
ERROR: expected: 10952217a6d404de8bf8a997fbea9b88f682df1fe98cb9b9f467ade641525639
ERROR: got : 165abf92cc04b39e80d29cadea7a6a7e8fddf59407d4ad2616507a7ebe8216f9
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
the hash of the license file needs to be updated, with an explanation
in the commit log detailing why the license file changed (especially to
confirm that there's no impact on the licensing conditions).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-05 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 11:52 [Buildroot] [PATCH 1/1] package/libavif: security bump to version 1.1.1 Adrian Perez de Castro
2024-08-05 13:48 ` Thomas Petazzoni via buildroot [this message]
2024-08-06 8:08 ` [Buildroot] [PATCH v2] " Adrian Perez de Castro
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=20240805154856.41f06fb1@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=thomas.petazzoni@bootlin.com \
/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