On Mon 2019-04-01 20:32:04 -0700, Jon Callas wrote:
I view this as primarily an implementation issue.
If I were to write that section, I’d put both Argon2i and Argon2d
in. There are reasons to go with either, and I’d leave that to the
implementation.
Interoperability matters only when you transfer keys from one
implementation to another, and as time goes on that is less and less
of a problem. (And the grumpy part of me says that if you’re going to
transfer to some new implementation, maybe you want a new key, anyway
even as I know that’s not friendly.)
It's not quite this simple, as S2K is also used in SK-ESK's (as Neal
points out elsewhere in this thread). So that means
"password-protected" OpenPGP messages, which are very often exchanged
between parties, so interoperability is important.
having both specs in the standard makes interop more challenging, so it
would be better to just have one if possible.
--dkg
signature.asc
Description: PGP signature
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp