On 011204, at 21:42:48, Gerhard Siegesmund wrote
> [...]  I tried to create a small script which automatically
> verifies pgp-signed mails from mutt.  [...]  It already works with
> inline-signatures. Simple script, simple output. For the
> mime-signed mails it doesn't work. :-(
> 
> Signed mail in file testmail. Using munpack I get signature (part2) and
> text (part1)
> 
> munpack -t testmail
> 
> Now I thought using 
> 
> gpg --verify part2 part1
> 
> should verify the signature. But it doesn't work.

The attached messages from Thomas Roessler explains why that method
doesn't work.

-- 
David Ellement
--- Begin Message ---
On 2000-10-03 01:45:02 +0300, Eugene Paskevich wrote:

>       Can you explain what do you mean? app/pgp is Content-Type;
>       but what is PGP/MIME? And is it the way decide my problem?

PGP/MIME is what mutt uses to send pgp-encrypted and -signed
messages.  The idea is basically this: You take the message, then
MIME-encode it entirely.  The result looks like this (for example):

        Content-Type: text/plain; charset=iso-8859-1
        Content-Transfer-Encoding: quoted-printable
        
        This attachment contains umlauts: =E4=F6=FC=DF

Now, this entire MIME body part is encrypted/signed, and eventually
put into some more MIME sugar.  Here, PGP only ever touches us-ascii
text (with which it deals nicely); the actual character set
conversions are left to the software which interprets the inner MIME
layers.

-- 
Thomas Roessler                         <[EMAIL PROTECTED]>

--- End Message ---

Reply via email to