On 010205, at 09:46:27, Nollaig MacKenzie wrote
> On 2001.02.05 08:34:45, you,
>  the extraordinary Åsmund Skjæveland, opined:
> > > I don't like to automatically check signatures on message opens,
> > > but I'd like to be able to do it manually, yet I can't find a
> > > command to do this.
> > > 
> > > I'm not talking about setting pgp_verify_sig but rather a command
> > > that I can issue to do this at any time while viewing the message.
> > 
> > Press "|" (pipe to command) and type "gpg --verify"?
> 
> Curiously, this gives a different result from the check
> done by Mutt's invocation of GPG;

See the attached message from Thomas Roessler for an explanation of
PGP/MIME.  Piping doesn't include the MIME headers, so the signature
won't be valid.

-- 
David Ellement


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]>



Reply via email to