[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: 8Bit chars in --armor output? GnuPG Bug? (was: Re: [PATCH] use
From:       Marc Mutz <Marc.Mutz () uni-bielefeld ! de>
Date:       2001-07-31 10:51:03
[Download RAW message or body]

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

On Monday 30 July 2001 23:16, Ingo Klöcker wrote:
<snip>
> I still don't like the idea that the users can't use a self-defined
> comment. It's an easy work around for us. But I guess not all GnuPG
> users will like it.
> Maybe we could remove the comment line only if it contains non-ASCII
> characters and warn the user that we removed it because non-ASCII
> characters aren't allowed in the comment. This makes the
> implementation a little bit harder for us but IMHO it's a good
> compromise.
>

ACK. But the next version of gpgme will contain exactly this 
workaround. OTOH, the next version of GnuPG will probably disallow 8bit 
chars in comments, so that the problem will be solved there. We could 
leave the dirty stuff of working around the comment problem for gnupg 
<= 1.0.6 to gpgme, then.

> This option doesn't cause any problems as we always force GnuPG to
> respond in english, i.e. all GnuPG generated output is in ASCII. We
> should definitely keep the version header.
<snip>

ACK.

Marc

- -- 
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

iD8DBQE7ZqRg3oWD+L2/6DgRAlvNAKDa4F79Kx9f3dydJ2shIA0TJUp02QCeKAOA
wUP+2nGgsSKvaN8Ns87ghzU=
=Urv6
-----END PGP SIGNATURE-----
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]