Gnus development mailing list
 help / color / mirror / Atom feed
From: Ivan Boldyrev <boldyrev@uiggm.nsc.ru>
Subject: Re: Trailing whitespace and PGP/MIME
Date: Tue, 30 Dec 2003 19:12:49 +0600	[thread overview]
Message-ID: <9boetq1mb2.fsf@cgitftp.uiggm.nsc.ru> (raw)
In-Reply-To: <ilu3cb235kz.fsf@latte.josefsson.org>

On 8608 day of my life Simon Josefsson wrote:
>> PGP/MIME uses detached signatures, that cannot be verified with
>> piping.
>
> Well... technically, it can be verified by piping after glueing the
> detached signature together with the data.  I believe Gnus uses this
> if you use Mailcrypt as the backend, because mailcrypt can't verify
> detached signatures.

If you do preprocessing such as gluing, you can do MIME decoding as
well :)

>> My opinion is that whitespaces must be removed from PGP/MIME-encoded
>> messages but not from Plain PGP-encoded ones.
>
> I agree for PGP/MIME, and probably for plain PGP as well (although the
> number of problems with plain PGP and CTE's have almost made me
> consider it a lost cause).

Plain PGP is considered harmful :) So it is up to message composer
responsibility to deal with "^From" and " $" in Plain PGP messages.

BTW, some MTA can decode one-part MIME-encoded messages and deliver
them as 8bit, for example.  But multipart messages (and PGP/MIME) are
never decoded by correct MTA.  So, even if we will encode Plain PGP
messages, it will be probably decoded anyway.  So, it is useless.

Plain PGP must be supported, but with note: NO WARRANTY.  THERE IS NO
WARRANTY OF CORRECT DELIVERY OF PLAIN PGP MESSAGES.  USE IT ON YOU OWN
RISK.

>> But it is current state of Gnus, isn't it?
>
> I don't think so, I was able to reproduce the problem with PGP/MIME
> too.  However, this patch should fix it.
>
> --- mm-bodies.el.~6.29.~	2003-12-26 06:32:11.000000000 +0100
> +++ mm-bodies.el	2003-12-30 12:26:57.000000000 +0100
> @@ -132,7 +132,8 @@
>      (cond
>       ((and (not longp)
>  	   (not (and mm-use-ultra-safe-encoding
> -		     (save-excursion (re-search-forward "^From " nil t))))
> +		     (save-excursion (or (re-search-forward "^From " nil t)
> +					 (re-search-forward " $" nil t)))))

It's is better to do encoding always if we use PGP/MIME.  Or even use

          (not mm-use-ultra-safe-encoding)

>> BTW, is gnus-bug archived somewhere?
>
> See <nntp://quimby.gnus.org/gnus.gnus-bug>.

Cool :)

I use leafnode, so I don't see that articles at quimby never expire...

-- 
Ivan Boldyrev

                      У женщины легче получить прощение, чем разрешение.



  reply	other threads:[~2003-12-30 13:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30  2:15 Jesper Harder
2003-12-30  9:04 ` Ivan Boldyrev
2003-12-30 11:31   ` Simon Josefsson
2003-12-30 13:12     ` Ivan Boldyrev [this message]
2003-12-30 11:05 ` Simon Josefsson
2003-12-30 13:02   ` Jesper Harder
2003-12-30 20:56     ` Simon Josefsson
2003-12-30 23:29       ` Jesper Harder
2003-12-30 23:52         ` Simon Josefsson
2003-12-31  0:01           ` Russ Allbery
2003-12-30 23:46       ` Russ Allbery
2003-12-31  0:05         ` Simon Josefsson
2003-12-31  2:26           ` Russ Allbery

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=9boetq1mb2.fsf@cgitftp.uiggm.nsc.ru \
    --to=boldyrev@uiggm.nsc.ru \
    /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).