From: "Ludovic Courtès" <ludo@gnu.org>
To: "Niels Möller" <nisse@lysator.liu.se>
Cc: 47222@debbugs.gnu.org, nettle-bugs@lists.lysator.liu.se
Subject: bug#47222: Serious bug in Nettle's ecdsa_verify
Date: Thu, 25 Mar 2021 10:51:51 +0100 [thread overview]
Message-ID: <87h7kzblxk.fsf_-_@gnu.org> (raw)
In-Reply-To: <875z1kl24h.fsf@netris.org> (Mark H. Weaver's message of "Sun, 21 Mar 2021 15:47:47 -0400")
Hi Niels,
> I've prepared a new bug-fix release of Nettle, a low-level
> cryptographics library, to fix a serious bug in the function to verify
> ECDSA signatures. Implications include an assertion failure, which could
> be used for denial-of-service, when verifying signatures on the
> secp_224r1 and secp521_r1 curves. More details in NEWS file below.
>
> Upgrading is strongly recomended.
Are there plans to make a new 3.5 release including these fixes?
Alternatively, could you provide guidance as to which commits should be
cherry-picked in 3.5 for downstream distros?
I’m asking because in Guix, the easiest way for us to deploy the fixes
on the ‘master’ branch would be by “grafting” a new Nettle variant
ABI-compatible with 3.5.1, which is the one packages currently depend on.
Thanks in advance,
Ludo’.
next prev parent reply other threads:[~2021-03-25 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cpfh7lbmsgz.fsf@slartibartfast.lysator.liu.se>
2021-03-18 0:21 ` bug#47222: Serious bug in Nettle's ecdsa_verify Mark H Weaver
2021-03-21 19:47 ` bug#47222: [Niels Möller] ANNOUNCE: Nettle-3.7.2 Mark H Weaver
2021-03-25 9:51 ` Ludovic Courtès [this message]
2021-03-25 16:21 ` bug#47222: Serious bug in Nettle's ecdsa_verify Niels Möller
2021-03-25 18:16 ` Leo Famulari
2021-04-16 20:46 ` Ludovic Courtès
2021-04-06 11:09 ` Léo Le Bouter via Bug reports for GNU Guix
2022-08-08 17:11 ` bug#47222: paren--- via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7kzblxk.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=47222@debbugs.gnu.org \
--cc=nettle-bugs@lists.lysator.liu.se \
--cc=nisse@lysator.liu.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).