Gnus development mailing list
 help / color / mirror / Atom feed
From: Jeremy Maitin-Shepard <jbms@attbi.com>
Subject: Re: GNUS "PGP Sign" bug (CVS Gnus)
Date: Sun, 28 Dec 2003 17:49:17 -0500	[thread overview]
Message-ID: <87smj4r21e.fsf@jbms.ath.cx> (raw)
In-Reply-To: <m34qvkppt6.fsf@merlin.emma.line.org> (Matthias Andree's message of "Sun, 28 Dec 2003 22:58:45 +0100")

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

Matthias Andree <ma+gnus@dt.e-technik.uni-dortmund.de> writes:

> Hi,
> it seems that GNUS' non-MIME "PGP Sign" (<#secure method=pgp mode=sign>)
> is a bit overzealous with MIME encoding, it trashes the boundaries by
> encoding the "-" in the leftmost column to "=2D". It should leave
> the ----- boundaries alone - these need to be encoded BEFORE signing,
> NOT AFTER signing.

The problem there is that Gnus is not adding the header:
Content-Transfer-Encoding: quoted-printable

It also messes up certain things by decoding the plaintext messages as
if it were quoted printable before signing and then re-encoding.

Strangely enough, this only seems to be broken in CVS Gnus.  Non-CVS
Gnus doesn't have that problem, so it must have been broken recently.
However, I didn't see any obvious reason for the problem when looking
at the sources.

> [snip]

-- 
Jeremy Maitin-Shepard

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-12-28 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28 21:58 Matthias Andree
2003-12-28 22:49 ` Jeremy Maitin-Shepard [this message]
2003-12-28 22:55 ` Jesper Harder
2003-12-29  0:52   ` Matthias Andree

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=87smj4r21e.fsf@jbms.ath.cx \
    --to=jbms@attbi.com \
    /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).