From: Andreas Enge <andreas@enge.fr>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57576@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
57599@debbugs.gnu.org, "Zhu Zihao" <all_but_last@163.com>
Subject: bug#57576: bug#57599: [PATCH] openpgp: Add support for ECDSA with NIST curves.
Date: Wed, 7 Sep 2022 14:02:37 +0200 [thread overview]
Message-ID: <YxiIXYVwrstSQqNL@jurong> (raw)
In-Reply-To: <86368af7-152b-f943-4ee6-e1471d3cb20c@telenet.be>
Am Wed, Sep 07, 2022 at 01:13:25PM +0200 schrieb Maxime Devos:
> Also, we _do_ have concrete evidence that the curves are flawed -- the website
> on the link mentions many issues in the process
The website (you mean the blog by D. Bernstein?) also mentions the use of
a hash function to arrive at the parameters. Maybe I overlooked something,
but I did not find other mentions of the curves (but I did not read the
page from A to Z).
> past that the NSA is in the habit of subverting communications.
But this is not concrete evidence that these curves are flawed.
As far as is publicly known, there are a few weak (and sparse) classes
of insecure elliptic curves, and the NIST curves do not belong to them.
So the only way these curves could be flawed is that there is an unknown
class of insecure curves, where the insecurity is known by the NSA.
Then if this class is sufficiently dense, one could start with a random
seed, hash the seed, and repeat until one obtains a weak instance;
see this link by a well-known cryptologist
https://miracl.com/blog/backdoors-in-nist-elliptic-curves/
and the link given there (to another post by Bernstein).
This is possible, but speculation instead of evidence.
Newer constructions are better, but not perfect; optimally one would want
a process of "generation of public random numbers" as described here:
https://eprint.iacr.org/2015/366
> Channels are for sharing things between multiple people. The keys are for
> authenticating channels. As multiple people are involved for a channel, this
> seems be be a non-personal decision by definition.
I said "political", which fits well the setting of multiple people involved.
And I meant this in opposition to "scientific", given the lack of evidence
against the NIST curves.
Andreas
next prev parent reply other threads:[~2022-09-07 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 11:53 bug#57576: Missing support for NIPT-P384 gpg algorithm in Guix channel authentication Zhu Zihao
2022-09-05 16:06 ` Ludovic Courtès
[not found] ` <20220905160929.21742-1-ludo@gnu.org>
[not found] ` <8735d4zpcf.fsf_-_@gnu.org>
2022-09-06 15:26 ` bug#57576: bug#57599: [PATCH] openpgp: Add support for ECDSA with NIST curves Zhu Zihao
2022-09-06 16:10 ` Maxime Devos
2022-09-06 20:02 ` Ludovic Courtès
2022-09-07 10:34 ` Andreas Enge
[not found] ` <86368af7-152b-f943-4ee6-e1471d3cb20c@telenet.be>
2022-09-07 12:02 ` Andreas Enge [this message]
2022-09-07 12:51 ` Ludovic Courtès
2022-09-07 15:27 ` zimoun
2022-09-24 9:53 ` Ludovic Courtès
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=YxiIXYVwrstSQqNL@jurong \
--to=andreas@enge.fr \
--cc=57576@debbugs.gnu.org \
--cc=57599@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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).