Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/libopenssl: security bump to version 3.2.1
Date: Sat, 16 Mar 2024 21:46:53 +0100	[thread overview]
Message-ID: <87o7bdnbuq.fsf@48ers.dk> (raw)
In-Reply-To: <20240211214348.E9E8A877CD@busybox.osuosl.org> (Yann E. MORIN's message of "Sun, 11 Feb 2024 22:43:00 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > commit: https://git.buildroot.net/buildroot/commit/?id=ce4d278739953c830cea0c017836f26ceabef63a
 > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

 > And drop the now upstreamed patches.

 > Fixes the following (low severity) issues:

 > - CVE-2023-6129 POLY1305 MAC implementation corrupts vector registers on
 >   PowerPC
 >   https://www.openssl.org/news/secadv/20240109.txt

 > - CVE-2023-6237 Excessive time spent checking invalid RSA public keys
 >   https://www.openssl.org/news/secadv/20240115.txt

 > - CVE-2024-0727 PKCS12 Decoding crashes
 >   https://www.openssl.org/news/secadv/20240125.txt

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

For 2023.11.x I have instead bumped to 3.1.5, which contains the same
fixes.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-03-16 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 21:43 [Buildroot] [git commit] package/libopenssl: security bump to version 3.2.1 Yann E. MORIN
2024-03-16 20:46 ` Peter Korsgaard [this message]

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=87o7bdnbuq.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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