Re: Entering passphrase twice when sending PGP signed message

[Matthias Andree <ma@dt.e-technik.uni-dortmund.de>]

Simon Josefsson <jas@extundo.com> writes:

> This happens if you use Gcc, and it is because the message is encoded
> once for sendmail/SMTP/NNTP and once for the Gcc copy, as you assume.
> But this can't be fixed easily, because the copy that is Gcc'ed is not
> the same as the one that is mailed or posted.

That's a bug then. The local copy must be identical to what's sent out,
save for the standardized differences (Newsgroups: potentially).

> An extreme example is the `gnus-gcc-externalize-attachments', which
> make Gcc differ distinctly from the SMTP/NTTP version of the mail.
> The more subtle examples are charset handling, news differ from mail,
> so making gcc equal one of them still wouldn't solve the problem in
> general.

As long as the whole "object" conforms to the intersection of RFC-2822
and RFC-1036, there's not much difference that matters for local storing
of what has been sent a second before.

> Another approach would be to attack the source of the problem,
> passphrases.  The gpg-agent seems like a good solution to that.

The problem appears to be that the saved article differs from the sent
article, which is a no-no.

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95