From: Simon Josefsson <jas@extundo.com>
Subject: Re: pgp 6.5.8 and gnus
Date: Tue, 27 Jul 2004 18:55:28 +0200 [thread overview]
Message-ID: <ilu3c3die4f.fsf@latte.josefsson.org> (raw)
In-Reply-To: <u8zd62h79at.fsf@mm117419-pc.MITRE.ORG>
David S Goldberg <david.goldberg6@verizon.net> writes:
>>>>>> On Tue, 27 Jul 2004 01:07:31 +0200, Simon Josefsson
>>>>>> <jas@extundo.com> said:
>
>> You could try GnuPG. Or the patch below.
>
> From a past experience I thought that GnuPG wouldn't be compatible.
With what? I haven't had compatibility problems with modern GnuPG,
except when corresponding to PGP 2.x users, but then the problem is
really that PGP 2.x doesn't implement OpenPGP. Some painful code has
been added, so that Gnus generate, using PGG/GnuPG, messages that can
be read even by RFC 1991 compatible implementations, like PGP 2.x.
IIRC, one example was that RFC 1991 doesn't ignore trailing white
space, as in the '-- ' signature separator, but RFC 2440 does. But if
you use AES, it isn't likely that PGP 2.x will be able to read it
anyway.
next prev parent reply other threads:[~2004-07-27 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 21:32 David S Goldberg
2004-07-26 23:07 ` Simon Josefsson
2004-07-27 15:35 ` David S Goldberg
2004-07-27 16:55 ` Simon Josefsson [this message]
2004-07-27 17:01 ` David S Goldberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilu3c3die4f.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).