On 5/7/26 17:44, Loup Vaillant wrote:
However, one thing is a specification and the other thing is running
code.
Wait a minute, are you saying that running code comes first, and specs
are meant to play catch up? At the beginning of the standardisation
process that makes a ton of sense, but once the standard is
established, it should take precedence.
Now in 2026, the onus is on GnuPG to follow OpenPGP,
the same way GCC is complying to the C and C++ standards.
My understanding is that there exists an OpenPGP v5 ("LibrePGP") and
OpenPGP v6 ("OpenPGP", the latest RFC); GnuPG currently implements v4
and v5 with no current plans to support v6 while others are implementing
v4 and v6 with no plans to support v5.
-- Jacob
_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users
