From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Sergio Prado <sergio.prado@e-labworks.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wolfssl: bump to version 5.5.3
Date: Sat, 5 Nov 2022 22:00:55 +0100 [thread overview]
Message-ID: <20221105220055.464ea2f6@windsurf> (raw)
In-Reply-To: <20221103225224.6375-1-fontaine.fabrice@gmail.com>
On Thu, 3 Nov 2022 23:52:24 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix for possible buffer zeroization overrun introduced at the end of
> v5.5.2 release cycle in GitHub pull request 5743 (#5743) and fixed in
> pull request 5757 (#5757). In the case where a specific memory
> allocation failed or a hardware fault happened there was the potential
> for an overrun of 0’s when masking the buffer used for (D)TLS 1.2 and
> lower operations. (D)TLS 1.3 only and crypto only users are not affected
> by the issue. This is not related in any way to recent issues reported
> in OpenSSL.
>
> https://github.com/wolfSSL/wolfssl/releases/tag/v5.5.3-stable
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/wolfssl/wolfssl.hash | 2 +-
> package/wolfssl/wolfssl.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
It's a version bump, but really a pure bug fix release, with very
limited changes, so I decided to take it in master. Applied, 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:[~2022-11-05 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 22:52 [Buildroot] [PATCH 1/1] package/wolfssl: bump to version 5.5.3 Fabrice Fontaine
2022-11-05 21:00 ` Thomas Petazzoni via buildroot [this message]
2022-11-14 15:47 ` Peter Korsgaard
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=20221105220055.464ea2f6@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=sergio.prado@e-labworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.