From: Peter Korsgaard <peter@korsgaard.com>
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: security bump to version 5.6.4
Date: Tue, 31 Oct 2023 19:04:17 +0100 [thread overview]
Message-ID: <8734xq1xem.fsf@48ers.dk> (raw)
In-Reply-To: <20231031145830.14831-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Tue, 31 Oct 2023 15:58:30 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> [Medium] A fix was added, but still under review for completeness, for a
> Bleichenbacher style attack, leading to being able to decrypt a saved
> TLS connection and potentially forge a signature after probing with a
> large number of trial connections. This issue is around RSA decryption
> and affects static RSA cipher suites on the server side, which are not
> recommended to be used and are off by default. Static RSA cipher suites
> were also removed from the TLS 1.3 protocol and only present in TLS 1.2
> and lower. All padding versions of RSA decrypt are affected since the
> code under review is outside of the padding processing. Information
> about the private keys is NOT compromised in affected code. It's
> recommended to disable static RSA cipher suites and update the version
> of wolfSSL used if using RSA private decryption alone outside of TLS.
> https://github.com/wolfSSL/wolfssl/releases/tag/v5.6.4-stable
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-31 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 14:58 [Buildroot] [PATCH 1/1] package/wolfssl: security bump to version 5.6.4 Fabrice Fontaine
2023-10-31 18:04 ` Peter Korsgaard [this message]
2023-11-01 11:16 ` 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=8734xq1xem.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=sergio.prado@e-labworks.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.