[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-28 10:08:24
[Download RAW message or body]

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

On Saturday, 28. July 2001 01:27, Marc Mutz wrote:
> On Friday 27 July 2001 23:14, Malte Starostik wrote:
> > Because that comments is not a property of the key but your local
> > preferences (or --comment argument). Try this one :)
> > gpg --export --armor --comment "Ümläüts" 0x30E0B9D8
>
> Ok. I see. Then this is a GnuPG-Bug. It should _not_ allow 8bit in
> --armor output. If the user tries to shoot in his foot, gnupg should
> issue a warning (or better: error and quit).
>
> Of course, this is easily "fixed" by the --default-comment option.

I'm against the usage of the --default-comment option. As Werner 
pointed out OpenPGP doesn't forbid the usage of non ASCII characters in 
the headers of the ASCII armor. We shouldn't force the user to forgo 
the possibility to use a self defined comment (cf. below that this 
option is used by some GnuPG users). Some corporations using PGP might 
even require a self defined comment header.
Therefore we should IMHO use quoted-printable encoding for 
application/pgp-keys attachments. Alternatively we could check if the 
armor headers contain only non ASCII characters and use 7bit encoding 
in this case.

Have a look at this (gnupg is the folder for the gnupg-users ML):
- --------------------
ingo@erwin:~ > grep "^Comment: " Mail/gnupg | sort | uniq
Comment: Anthony E. Greene <agreene@pobox.com> 0x6C94329D
Comment: Exmh version 2.3.1 01/18/2001
Comment: For info see http://www.gnupg.org
Comment: Get my Public Key here - http://pgpkey.ac-martin.com
Comment: GPG Sealed for freshness
Comment: http://www.gnupg.org
Comment: I'm out of my mind, but feel free to leave a message.
Comment: Join PGP-Basics: PGP-Basics-subscribe@yahoogroups.com
Comment: Keyid: 0x7B251671
Comment: keyserver http://pgpkeys.mit.edu:11371
Comment: Made by M.P.O.
Comment: OpenPGP encrypted mail preferred.  See <http://www.gnupg.org/>
Comment: PGP-Basics-Firewalls-subscribe@yahoogroups.com
Comment: PGP-Basics-subscribe@yahoogroups.com
Comment: pgpenvelope 2.10.0 - http://pgpenvelope.sourceforge.net/
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/
Comment: pgpenvelope - http://www.uiuc.edu/ph/www/ftobin/resources.html
Comment: Please encrypt and sign for internet security
Comment: Please encrypt or sign for internet security
Comment: Pour information voir http://www.gnupg.org
Comment: Powered By Becky!2
Comment: Powered By Becky!2, The Ultimate Email Program
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard 
<http://www.gnupg.org/>
Comment: processed by Mulberry PGP Plugin
Comment: signed, sealed, delivered ...  Key-ID : 0x931C9A9F
Comment: Ubi libertas, ibi patria.
Comment: Weitere Infos: siehe http://www.gnupg.org
- --------------------

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

iD8DBQE7Yo8YGnR+RTDgudgRAvnyAKDfpJnH2DSUwJXlm9GOwrsc890X1gCgqWMM
EaZIMta6Uo7iMjMWgKQe9+o=
=+Qf9
-----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]