How to batch generate ECC key

Rezart Qelibari für GnuPG gnupg-kontakt at rezart.qelibari.de
Fri Dec 29 16:53:27 CET 2017


Thank you so much! This did the trick! I am very impressed.

I don’t want to bother you too much, but maybe you can answer me the two follow-up questions:

- How did you find out the protocol names, especially the upper case „E“ of „Ed25519“ and that „cv25519“ is actually named „Curve25519“? Although „gpg --expert --full-generate-key“ correctly states  „Curve 25519“, „gpg -k“ still yields „cv25519“. I find this behaviour very strange and unwisely.

- Why do the algorithm ids (22 for „Ed25519“ and 18 for „Curve25519“) not work?

In both cases I looked up both gpg and libgcrypt documentations and found no hint on that behaviour at all.

On 29. December 2017 at 15:16:07, Kristian Fiskerstrand (kristian.fiskerstrand at sumptuouscapital.com) wrote:

try:  
$ cat config.txt  
Key-Type: eddsa  
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20171229/f8e2c485/attachment.html>


More information about the Gnupg-users mailing list