Re: [openpgp] don't emit version armor header by default

On Mon 2021-05-03 20:58:15 +0200, ilf wrote:
> This is rough consensus and running code in all implementations I can 
> find:
>
> GnuPG: 
> https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=c9387e41db7520d176edd3d6613b85875bdeb32c
> GPGTools: 
> https://github.com/GPGTools/MacGPG2/commit/831c2ed77d2ce88134ad4d689414051dc99dc3b3
> SKS: https://bitbucket.org/skskeyserver/sks-keyserver/commits/4af75b3526d9
> LibTMCG: 
> http://git.savannah.nongnu.org/cgit/libtmcg.git/commit/?id=2c8a6861ab839cb58b6483a04a7b584423a27811
>
> If this gets adopted, we should probably remove it from this example: 
> https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-03.html#name-example-of-an-ascii-armored
Hearing no complaints or objections, i've opened this merge request
following ilf's recommended wording:

   https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/45

Regards,

   --dkg

signature.asc
Description: PGP signature

_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp