non-ASCII armor headers

[Thomas Roessler]

--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

GnuPG has a localized default "Comment" ASCII armor header, which is=20
not restricted to us-ascii in certain locales.

This behaviour breaks PGP/MIME, and is generally incompatible with=20
the expectation that ASCII armor is restricted to ASCII.

I'd suggest (1) to restrict the default value of that header to=20
something which is us-ascii independent of the user's locale, (2) to=20
make sure that this header isn't set to something non-ascii by=20
users, and (3) to make it possible to easily disable that header.

--=20
Thomas Roessler                        http://log.does-not-exist.org/

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: none

iQEVAwUBO2PZStImKUTOasbBAQL6PwgAmjIrbRX8UvHgwxYxf1IUGpq+c+FHGoTN
JLF/xha3WkWX7hXEDa9MxgBBlaolGyNunxPoImjLJ1c7NOMObC4NjXlJqJ+PXac0
pMhZFZ4rkFyyHghgI1zH6NiLkcXi4y7DZcS5yq8RGspBiJLxexZxuSK+p4JeobbD
UNvpN+V+uT5dzcp8ZFsMoS9b5p8evNQe818b75tIf+K2cb96dl5iHAuX1anYoj7+
pKJskMJTPkUWOiHZrPD32pEhlFHys/vTaBA5gPyggKFLihYp3Pcis7zLa1m0ojvi
oaOWqUtmlI+8gTEjtHmYYp30b62S2R/2UO/jYI6vgTR9GYBeFSOcKA==
=uouV
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--