Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: mml1991.el patch (was gpg.el)
Date: Wed, 01 May 2002 12:37:15 +0200	[thread overview]
Message-ID: <87r8kw17dw.fsf@deneb.enyo.de> (raw)
In-Reply-To: <7kmqjt4d.fsf@mail.ru> (Dmitry Bely's message of "Mon, 29 Apr 2002 21:45:54 +0400")

Dmitry Bely <dbely@mail.ru> writes:

> OK, that's not the gpg.el bug. The problem is that
>
> (1) (mm-body-encoding) does not allow 8bit encodings for PGP-signed
>     messages and returns base64 for some code pages (e.g. for Russian
>     koi8r)

For clearsigned messages (that's the stuff mml1991.el is for), or for
OpenPGP/MIME-signed messages?  It should be necessary only in the
latter case.

> (2) (mml1991-gpg-sign) always assumes that it gets qp-encoded text, so it
>     fails if base64-encoded one is supplied.
>
> Here is the patch that fixes this issue (I am neither the very experienced
> Lisp programmer nor Gnus hacker, so if you feel that I did something the
> wrong, please correct me)

IMHO, your change is wrong from an architectural point of
view. mml1991.el signatures should be applied *after* we have
generate the octet stream which is to be sent, but *before*
Content-Transfer-Encoding is applied.

But I'll check with OpenPGP WG to be sure that this is the right
approach to clearsigned messages and MIME.



  reply	other threads:[~2002-05-01 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 12:08 gpg.el Dmitry Bely
2002-04-26 15:28 ` gpg.el Florian Weimer
2002-04-26 16:02   ` gpg.el Dmitry Bely
2002-04-29 17:45     ` mml1991.el patch (was gpg.el) Dmitry Bely
2002-05-01 10:37       ` Florian Weimer [this message]
2002-05-01 15:33         ` Dmitry Bely

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=87r8kw17dw.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    /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).