GnuPG modern can't genereate keys on my Windows

Ivan Markin twim at
Wed Sep 2 18:30:59 CEST 2015

Werner Koch:
> That is actually on purpose.  Both are based on the same curve and it
> seems easier to just call it Curve25519 than to explain why we use a
> different variant for signing.  After all Curve25519 is a well known
> term.
Sounds almost reasonable. But why then GnuPG shows Ed25519 keys as eg.
'ed25519/52275F7A'? When someone trying to generate 'Curve25519-signing
key' they'll get ed25519 key. "Maybe I've done something wrong? I should
regenerate my signature key...". In my opinion it's a little bit confusing.
The fact that both Ed25519 and Curve25519 are based on the same curve
one can easily note from '25519' in their names.
Actually Ed25519 is a birational equivalent to Curve25519; it's not a
Curve25519. So I think that GnuPG should use exact naming for what it uses.

Ivan Markin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20150902/0c9debe3/attachment-0001.sig>

More information about the Gnupg-users mailing list