[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 7bit instead of base64 for applic
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2001-07-31 22:08:59
[Download RAW message or body]

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

On Tuesday, 31. July 2001 14:28, Marc Mutz wrote:
> 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.

O.K.

BTW, I just checked if 8bit characters can appear in PGP armor headers. 
They can't! Neither PGP2.6.3in nor PGP5.0 nor PGP6.5.8 allow 8bit 
characters in the comment string.
So we don't have to work around the comment problem for PGP.

Regards,
Ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7Zyx7GnR+RTDgudgRAje1AJ42zNg9M5PvgTcwPfS5us/9OengoQCfRCWc
ifC1GdfcCBr9f69e3INnKZY=
=YBVg
-----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]