Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
Subject: Re: oddies with enigmail
Date: Tue, 19 Jul 2005 17:46:56 +0000	[thread overview]
Message-ID: <87u0iqk7sf.fsf@mat.ucm.es> (raw)
In-Reply-To: <iluoe8z6i3d.fsf@latte.josefsson.org>

>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:

    Simon> Werner Koch <wk@gnupg.org> writes:
    >> On Wed, 13 Jul 2005 18:29:03 +0000, Uwe Brauer said:
    >> 
    >>>  The   question is can I  clear   sign the  message  such that
    >>> enigmail would not complain?
    >> 
    >> Do you say  that pgg inserts the Hash  line?  This is obviously
    >> wrong - it is best to let gpg  create the cleas signed message.
    >> This will make sure that the correct header is used.

    Simon> PGG doesn't insert nor remove any  Hash: lines.  The output
    Simon>  from gpg  is used directly,  except  for QP encoding  when
    Simon> needed.   Gnus will QP encode  the output from gpg,  so the
    Simon> receiver  till  have to perform  QP decode  before it looks
    Simon> like  a valid OpenPGP packet.  This  might  break some MUAs
    Simon> that expect  the OpenPGP armor   to not be QP escaped,  but
    Simon> rather, only the signed data.   But such a message wouldn't
    Simon> conform to MIME specs (the '='  in the CRC24 tag is invalid
    Simon> QP unless escaped), and some MTAs bounce those messages...

    Simon> That the morale is to use PGP/MIME instead is hopefully obvious.

Well that is what I used
mml-secure-message-sign-pgpmime




  reply	other threads:[~2005-07-19 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 19:16 Uwe Brauer
2005-07-12 20:16 ` Werner Koch
2005-07-13 18:29   ` Uwe Brauer
2005-07-19 13:13     ` Werner Koch
2005-07-19 13:28       ` Simon Josefsson
2005-07-19 17:46         ` Uwe Brauer [this message]
2005-07-24 14:45           ` Simon Josefsson

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=87u0iqk7sf.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    /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).