8Bit chars in --armor output? GnuPG Bug? (was: Re: [PATCH] use 7bit instead of base64 for application/pgp-keys)

[Marc Mutz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 27 July 2001 23:14, Malte Starostik wrote:
> On Samstag, 28. Juli 2001 01:07, Marc Mutz wrote:
> > On Friday 27 July 2001 19:10, Ingo Kl=F6cker wrote:
> > <snip>
> > > The test message which you send me was broken. Therefore I'm not
> > > sure if 7bit encoding works. In theory it should work. At least
> > > if the user hasn't added some non 7bit characters to the Comment
> > > (or we overwrite the user defined comment by using the
> > > --default-comment option). For an example have a look at the
> > > attached key.
> > >
> > > IMHO 7bit encoding is not an option.
> > <snip>
> > If the --armor'ed output of gpg contains 8 bit characters, then
> > that is a bug in gpg and needs to be fixed ASAP. I don't see 8bit
> > chars in the output of
> > gpg --export --armor 0x30E0B9D8
> > though.
>
> Because that comments is not a property of the key but your local
> preferences (or --comment argument). Try this one :)
> gpg --export --armor --comment "=DCml=E4=FCts" 0x30E0B9D8
<snip>

Ok. I see. Then this is a GnuPG-Bug. It should _not_ allow 8bit in=20
- --armor output. If the user tries to shoot in his foot, gnupg should=20
issue a warning (or better: error and quit).

Of course, this is easily "fixed" by the --default-comment option.

What do the GnuPG folks say? (cc'ing)

Marc

- --=20
Marc Mutz <Marc@Mutz.com>
http://marc.mutz.com/
http://www.mathematik.uni-bielefeld.de/~mmutz/
http://EncryptionHOWTO.sourceforge.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7Yfj73oWD+L2/6DgRArc6AJ0R3LIMM5+Q9tUD7ygbBCzq1yITSQCfTMk5
PKSGV3wEbP39DfAfzLEOBo4=3D
=3DNYJ6
-----END PGP SIGNATURE-----