From: "Ludovic Courtès" <ludo@gnu.org>
To: 47222@debbugs.gnu.org
Subject: bug#47222: Serious bug in Nettle's ecdsa_verify
Date: Fri, 16 Apr 2021 22:46:50 +0200 [thread overview]
Message-ID: <87im4m2c05.fsf@gnu.org> (raw)
In-Reply-To: <cpfh7kzjjaj.fsf@slartibartfast.lysator.liu.se> ("Niels Möller"'s message of "Thu, 25 Mar 2021 17:21:40 +0100")
Hi!
(- Niels, - nettle-bugs)
nisse@lysator.liu.se (Niels Möller) skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Are there plans to make a new 3.5 release including these fixes?
>
> No, I don't plan any 3.5.x release.
>
>> Alternatively, could you provide guidance as to which commits should be
>> cherry-picked in 3.5 for downstream distros?
>
> Look at the branch release-3.7-fixes
> (https://git.lysator.liu.se/nettle/nettle/-/commits/release-3.7-fixes/).
> The commits since 3.7.1 are the ones you need.
>
> Changes to gostdsa and ed448 will not apply, since those curves didn't
> exist in nettle-3.5. Changes to ed25519 might not apply cleanly, due to
> refactoring when adding ed448.
I confirm these patches don’t apply, and I’m not comfortable fiddling
with that.
Leo and I checked and found that Debian doesn’t have 3.5. Do other
distros have backports of these patches to 3.5?
If not, our options are:
1. to invest in the backport ourselves, with good peer review, ideally
getting it stamped by Niels & co;
2. to wait until a full rebuild has come.
It’s not an ideal situation. Thoughts?
Ludo’.
next prev parent reply other threads:[~2021-04-16 20:47 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 ` bug#47222: Serious bug in Nettle's ecdsa_verify Ludovic Courtès
2021-03-25 16:21 ` Niels Möller
2021-03-25 18:16 ` Leo Famulari
2021-04-16 20:46 ` Ludovic Courtès [this message]
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=87im4m2c05.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=47222@debbugs.gnu.org \
/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).