From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/55403 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: Trailing whitespace and PGP/MIME Date: Wed, 31 Dec 2003 01:05:34 +0100 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <87n099yil9.fsf@windlord.stanford.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1072829153 31025 80.91.224.253 (31 Dec 2003 00:05:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 31 Dec 2003 00:05:53 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M3943@lists.math.uh.edu Wed Dec 31 01:05:50 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 1AbTrx-0007qk-00 for ; Wed, 31 Dec 2003 01:05:49 +0100 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 1AbTrr-0001Df-00; Tue, 30 Dec 2003 18:05:43 -0600 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1AbTrm-0001DV-00 for ding@lists.math.uh.edu; Tue, 30 Dec 2003 18:05:38 -0600 Original-Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178]) by justine.libertine.org (Postfix) with ESMTP id 14FEC3A0038 for ; Tue, 30 Dec 2003 18:05:38 -0600 (CST) Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.10/8.12.10) with ESMTP id hBV05aAU005534 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 31 Dec 2003 01:05:37 +0100 Original-To: Russ Allbery Mail-Copies-To: nobody X-Hashcash: 0:031231:rra@stanford.edu:12ec5092031b299c X-Hashcash: 0:031231:ding@gnus.org:7820788e3e2097c1 In-Reply-To: <87n099yil9.fsf@windlord.stanford.edu> (Russ Allbery's message of "Tue, 30 Dec 2003 15:46:42 -0800") User-Agent: Gnus/5.1004 (Gnus v5.10.4) Emacs/21.3.50 (gnu/linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:55403 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:55403 Russ Allbery writes: > Simon Josefsson writes: > >> Ah. Hm. Er. So what IS the right thing? The MUST above is for >> PGP/MIME, yes, but the _reason_ the MUST is there in the document is >> about as valid for plain PGP as it is for PGP/MIME, I think, arguing >> that the obvious approach is the right. > > It shouldn't be as valid for inline PGP. PGP implementations generally > handle trailing spaces without difficulty when processing attached > signatures (by stripping them before processing the message). Even pre-OpenPGP implementations? E.g., PGP 2.x. RFC 1991 does not mention "whitespace", "trailing", or "strip". Gnus currently claim to support them, although I'm not sure this is a good idea, nor if anyone actually uses PGP 2.x. >> One (non-)solution is to warn the user whenever the message content >> may not work reliably with plain PGP and ask the user if she wants to >> continue, or use PGP/MIME instead. > > This is going to get really annoying for people who use inline signatures > with a sig delimiter. > > The real solution is for people to stop using the broken inline PGP > signature standard and switch to PGP/MIME so that the true structure of > their messages is exposed to software, but it's so hard to convince people > of that.... So maybe an annoying blurb showing up every time users try to use inline PGP with non-ASCII, trailing whitespace, or dash escaped text, is the best we can hope to do. If we annoy people with the blurb, maybe they stop annoying us by using inline PGP. For pure-ASCII, no trailing whitespace, no possibly dash escaped text, use of inline isn't that bad, especially for announcements stored in files -- PGP/MIME is too e-mail specific to be used in that case.