ECC Ed25519/Curve25519 ready as default?

[Daniel Kahn Gillmor]

On Fri 2019-04-26 10:14:51 +0200, Andreas Heinlein wrote:
> Am 25.04.19 um 14:09 schrieb Bernhard Reiter:
>> Best would be to compile a list (e.g. in the wiki) 
>> as documented basis for a decision.
>
> Such a list should probably include frontend support as well, at least
> for the major frontends. AFAIK, GNOME seahorse does not, at least it
> does not offer creating ECC keys.

creating ECC keys isn't the issue here -- the issue at hand is
interoperability: if an implementation like GnuPG *does* default to
creating an Ed25519 key, how much of the deployed OpenPGP ecosystem will
fail to interoperate with such a key?

fwiw, i think GnuPG has been so entrenched that one of the main factors
for delay here will be with previous versions of GnuPG itself (someone
has already mentioned Debian Jessie on this thread).

But i agree that a list of commonly-used OpenPGP implementations, and
the versions at which they gained the ability to handle the different
ECC algorithms would be a useful thing to have.

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190426/98306f77/attachment.sig>