This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
PGP authentication in the RIPE Database.
- Previous message (by thread): PGP authentication in the RIPE Database.
- Next message (by thread): as-set syntax errors ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
noc at entire-systems.com
Tue Apr 24 20:02:54 CEST 2001
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
- Previous message (by thread): PGP authentication in the RIPE Database.
- Next message (by thread): as-set syntax errors ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]