From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/53963 Path: main.gmane.org!not-for-mail From: Matthias Andree Newsgroups: gmane.emacs.gnus.general Subject: Re: Entering passphrase twice when sending PGP signed message Date: Mon, 15 Sep 2003 01:12:15 +0200 Sender: ding-owner@lists.math.uh.edu Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1063581149 22381 80.91.224.253 (14 Sep 2003 23:12:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 14 Sep 2003 23:12:29 +0000 (UTC) Original-X-From: ding-owner+M2503@lists.math.uh.edu Mon Sep 15 01:12:28 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19yg2e-0004Tr-00 for ; Mon, 15 Sep 2003 01:12:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19yg2Y-00054N-00; Sun, 14 Sep 2003 18:12:22 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19yg2U-00054I-00 for ding@lists.math.uh.edu; Sun, 14 Sep 2003 18:12:18 -0500 Original-Received: (qmail 34165 invoked by alias); 14 Sep 2003 23:12:17 -0000 Original-Received: (qmail 34159 invoked from network); 14 Sep 2003 23:12:17 -0000 Original-Received: from pd951f1a0.dip.t-dialin.net (HELO m2a2.dyndns.org) (?3Iw8uPlk6oXXHOPxLNMW2eV5xQnJ12Yz?@217.81.241.160) by sclp3.sclp.com with SMTP; 14 Sep 2003 23:12:17 -0000 Original-Received: by merlin.emma.line.org (Postfix, from userid 500) id CD398823F5; Mon, 15 Sep 2003 01:12:15 +0200 (CEST) Original-To: ding@gnus.org In-Reply-To: (Simon Josefsson's message of "Sun, 14 Sep 2003 23:38:18 +0200") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.2 (gnu/linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:53963 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:53963 Simon Josefsson 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