Re: Entering passphrase twice when sending PGP signed message

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

Simon Josefsson <jas@extundo.com> writes:

> What purpose would this serve?  If you want a copy of what is sent in
> mail, there is Bcc.  I'm not sure if there is a similar feature for
> getting a copy of what is posted in news, though.

Not officially. Gcc: and Fcc: are local extensions to Gnus. Group carbon
copies are handled through "Newsgroups:" officially.

> The advantage of generate Gcc separately from mail and news is, of
> course, that your local copy isn't restricted to the arbitrary, and
> sometimes incompatible, limitations in mail and news,

What are these incompatible limitations?

> and to support Gcc rewriting functionality,
> e.g. gnus-gcc-externalize-attachments.

AFAICS, any News posting can be sent as a mail, technically, because
RFC-1036 requires a subset of RFC-2822. IOW, if Gnus only uses
constructs legal in News, we don't need this distinction except to
choose between SMTP and NNTP -- which is the posting-method in the first
place.

I wonder if there's anything that mail allows for but news doesn't
that's needed in real life.

> (The logic would have to, besides checking for the intersection
> between (2)822 and 1036(bis), also check if any of the enabled Gcc
> rewriting features would modify the "object".

The logic would be to only generate RFC-1036 + RFC-2045..2049 (+ 2231),
even for mail. I. e. 7bit US-ASCII headers, with limited folding and
limited RFC-2822 syntax.

Any archival or "keep a local copy" function MUST NOT tamper with the
content in any case, particularly not when the content is being
signed. gnus-gcc-externalize-attachments MUST NOT apply to signed
material.

> Even so, it must have knowledge about certain MML tags, such as
> security tags, which generate different output each time, but can
> (probably, and not in all situations) be considered equal, for Gcc:ing
> purposes.  Also remember that MIME encoding can be different in news
> than from mail too.)

How does MIME encoding for news differ from MIME encoding for mail?

All these possible differences look academic to me ATM. The real-world
differences are: Path vs. References and Newsgroups vs. To. That's it.

> There are already features that require the saved article to differ
> from what was sent, so it is not always a bad thing, assuming people
> do use those features.

I really wonder what features these are. Confusion Inductor v1.0 perhaps.

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95