From: Peter Korsgaard <peter@korsgaard.com>
To: Christian Stewart <christian@aperture.us>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] package/go: security bump to v1.20.7
Date: Thu, 31 Aug 2023 13:05:02 +0200 [thread overview]
Message-ID: <87r0njmq01.fsf@48ers.dk> (raw)
In-Reply-To: <20230801204830.175727-1-christian@aperture.us> (Christian Stewart's message of "Tue, 1 Aug 2023 13:48:30 -0700")
>>>>> "Christian" == Christian Stewart <christian@aperture.us> writes:
> go1.20.7 (released 2023-08-01) includes a security fix to the crypto/tls
> package, as well as bug fixes to the assembler and the compiler.
> Fixes CVE-2023-29409: restrict RSA keys in certificates to <= 8192 bits
> Extremely large RSA keys in certificate chains can cause a client/server to
> expend significant CPU time verifying signatures. Limit this by restricting the
> size of RSA keys transmitted during handshakes to <= 8192 bits.
> Based on a survey of publicly trusted RSA keys, there are currently only three
> certificates in circulation with keys larger than this, and all three appear to
> be test certificates that are not actively deployed. It is possible there are
> larger keys in use in private PKIs, but we target the web PKI, so causing
> breakage here in the interests of increasing the default safety of users of
> crypto/tls seems reasonable.
> https://go.dev/doc/devel/release#go1.20.7
> Signed-off-by: Christian Stewart <christian@aperture.us>
For 2023.02.x and 2023.05.x I have instead bumped to 1.19.12, which
contains the same fix.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-31 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 20:48 [Buildroot] [PATCH v1 1/1] package/go: security bump to v1.20.7 Christian Stewart via buildroot
2023-08-31 11:05 ` 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=87r0njmq01.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--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