From: Leo Famulari <leo@famulari.name>
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 14:16:50 -0400 [thread overview]
Message-ID: <YFzTkk51ufdpvDGD@jasmine.lan> (raw)
In-Reply-To: <cpfh7kzjjaj.fsf@slartibartfast.lysator.liu.se>
On Thu, Mar 25, 2021 at 05:21:40PM +0100, Niels Möller wrote:
> 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.
Okay.
> > 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.
>
> I still recommend upgrading to the latest version. There were an abi
> break in 3.6 (so you'd need to recompile lots of guix packages), but no
> incompatible changes to the (source level) api.
Unfortunately, non-ABI compatible upgrades of nettle cannot be done
quickly in Guix. As you point out, we'd have to recompile over >10000
packages, and then we'd have to fix any breakage that might occur from
the upgrade.
We will have to try to cherry-pick the bug fix patches.
next prev parent reply other threads:[~2021-03-25 18:22 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 [this message]
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=YFzTkk51ufdpvDGD@jasmine.lan \
--to=leo@famulari.name \
--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).