GnuPG 2.4.4 still using legacy packets?

[Werner Koch]

Hi!

Some background on why we have these compliance options: Back then when
we developed rfc2440, and later rfc4880, it was useful to have them to
test the changes we implemented in PGP and GnuPG.  The --pgp options
were also useful in the early days for an easy migration path from pgp2
to gpg; in particular in MUAs like Pine and such.

These days they are mostly useless because everyone demands MDC and it
is virtually impossible to keep the compliance options exactly up to the
respective specification.  But people are using them and thus it is hard
to remove the option.

The new generalized option --compliance is now used to restrict he GnuPG
behaviour to certain compliance requirements.  Currently only for the
German/EU/NATO compliance but maybe later also for FIPS.


Shalom-Salam,

   Werner


-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 284 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20251113/988f5fe9/attachment-0001.sig>