From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: broken: #secure method=pgp mode=signencrypt
Date: Wed, 09 Jul 2003 17:39:04 +0200 [thread overview]
Message-ID: <87k7arlnfr.fsf@deneb.enyo.de> (raw)
In-Reply-To: <20030709102948.GE3850@merlin.emma.line.org> (Matthias Andree's message of "Wed, 9 Jul 2003 12:29:48 +0200")
Matthias Andree <matthias.andree@gmx.de> writes:
> What I particularly take offense at is this allegation:
>
> Will cause Gnus to sign and encrypt in one pass, thus generating a
> single signed and encrypted part. Note that combined sign and encrypt
> does not work with all supported OpenPGP implementations (in
> particular, PGP version 2 do not support this).
>
> I have just verified this with mutt and pgp-2.6.3i, and pgp on the
> command line, it just works. It has always worked as long as I can
> remember. (Plus, PGP-2 certainly doesn't claim OpenPGP conformance, it's
> too old to.)
The problem is that GnuPG cannot encrypt + sign in one pass in a way
that yields a message that can be processed by PGP 2.6.x (even after
patching the necessary algorithms into PGP or GnuPG). This problem
does not arise if you sign and encrypt separately.
next prev parent reply other threads:[~2003-07-09 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 21:51 Matthias Andree
2003-07-09 6:06 ` Simon Josefsson
2003-07-09 10:29 ` Matthias Andree
2003-07-09 15:39 ` Florian Weimer [this message]
2003-07-09 16:06 ` Matthias Andree
2003-07-09 16:59 ` Simon Josefsson
2003-07-09 17:05 ` Simon Josefsson
2003-07-10 0:34 ` Matthias Andree
2003-07-10 2:39 ` Jan Rychter
2003-07-10 4:16 ` Simon Josefsson
2003-07-10 13:14 ` how to signencrypt with gpg for pgp2 (was: broken: #secure method=pgp mode=signencrypt) Matthias Andree
2003-07-10 13:19 ` Florian Weimer
2003-07-11 9:40 ` how to signencrypt with gpg for pgp2 Matthias Andree
2003-07-10 15:14 ` Simon Josefsson
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=87k7arlnfr.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).