From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Eliminate gpg-2comp default from gpg.el
Date: Wed, 26 Dec 2001 19:56:29 +0100 [thread overview]
Message-ID: <873d1xkdya.fsf@deneb.enyo.de> (raw)
In-Reply-To: <ilu4rmdvopp.fsf@extundo.com> (Simon Josefsson's message of "Wed, 26 Dec 2001 19:08:34 +0100")
Simon Josefsson <jas@extundo.com> writes:
> gpg-2comp is discussed in texi/gnus.texi, I'm not sure if the current
> wording is correct. Maybe that section could be extended into
> something that isn't GPG specific? There is some overlap between the
> message manual and the Gnus manual.
I've removed the paragraph, it was incorrect anyway. The --rfc1991
GnuPG option still generates DES-encrypted messages, which can only be
read by a tweaked PGP 2.6.x version. In addition, the --rfc1991 flag
does not take care of single-pass signature issues.
prev parent reply other threads:[~2001-12-26 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 11:08 Florian Weimer
2001-12-26 13:49 ` Simon Josefsson
2001-12-26 15:37 ` Florian Weimer
2001-12-26 18:08 ` Simon Josefsson
2001-12-26 18:56 ` Florian Weimer [this message]
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=873d1xkdya.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).