Robert J. Hansen wrote: > > RJH's answer sounds like a good piece of advice, but still, at the > > end, we HAVE to to choose which algorithm to use when creating new > > key pairs. > > rjh@maggie:~$ gpg --gen-key > gpg: WARNING: using experimental features from RFC4880bis! > Note: Use "gpg --full-generate-key" for a full featured key generation > dialog. > > GnuPG needs to construct a user ID to identify your key. > > Real name: Delete Me > Email address: del...@example.org > You selected this USER-ID: > "Delete Me <del...@example.org>" > > Change (N)ame, (E)mail, or (O)kay/(Q)uit? o > We need to generate a lot of random bytes. It is a good idea... > > [snip] > > Where in there was I ever asked to choose an algorithm?
In older versions, like 2.0.x for example, it asked for ... > "Unless you know what you're doing and why, use the defaults." I've > been saying that for twenty years now. I keep thinking that someday > someone will actually take it seriously... Super modern OpenPGP implementations like the super awesome sequoia pgp defaults to cv25519... (and does not need to generate a UID for privacy reasons, simply fantastic!) Regards Stefan -- Signal (Desktop) +4915172173279 https://keybase.io/stefan_claas _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users