PGP authentication in the RIPE Database.
Dear Colleagues, PGP updates are now possible again in the RIPE Database. We traced the source of the problem to a subtle bug. Currently, PGP signed messages encoded in quoted-printable text are not supported, but if anyone feels strongly about this, then this mailing list is the appropriate place to discuss it. If you have questions about the operation of the RIPE Database or the software, please contact <ripe-dbm@ripe.net>. Regards, A. M. R. Magee ______________ RIPE NCC
On Tue, Apr 24, 2001 at 07:56:18PM +0200, RIPE Database Administration wrote:
Currently, PGP signed messages encoded in quoted-printable text are not supported, but if anyone feels strongly about this, then this mailing list is the appropriate place to discuss it.
OK, you asked for it... :-) Quote from mutt's manual: 6.3.111. pgp_strict_enc Type: boolean Default: yes If set, Mutt will automatically encode PGP/MIME signed messages as quoted-printable. Please note that unsetting this variable may lead to problems with non-verifyable PGP signatures, so only change this if you know what you are doing. So I strongly advocate implementing q-p decoding capability into the MIME parser. Best regards, Daniel -- Entire Systems GmbH - Ferbachstrasse 12 - 56203 Hoehr-Grenzhausen, Germany InterNIC-Handle: ES1238-ORG RIPE-Handle: ESN10-RIPE Tel: +49 2624 9550-55 GnuPG/PGP Key-ID: 0xBF3C40C9 http://www.entire-systems.com/noc/noc-key.asc GnuPG/PGP Fingerprint: 1F3F B675 1A38 D87C EB3C 6090 C6B9 DF48 BF3C 40C9
participants (2)
-
Daniel Roesen -
RIPE Database Administration