On Wed, Jul 17, 2002 at 05:39:56AM -0500, David T-G spewed into the ether:
[clip]
> % Problem...
> % 
> % When I receive mime encoded msgs I can't read it and mutt reports that
> % the signature couldn't be verified even though the screen output
> % reports a good signature. And I can't read the msg unless I press v
> 
> You should check the exit code of gpg.  If it's nonzero and you haven't
> specifically set mutt to recognize "good signature text" then mutt will
> see it as a failure anyway.
> 
I set pgp_good_sign and now mutt/gpg verifies signatures on 
encrypted mime encoded msgs. But it still doesn't allow me to
decrypt the message. ESC-P doesn't work either..
> 
> % to go to the attachment menu.
> % Save the whole thing as a text file. Then I have to
> % run gpg --decrypt once which verifies the signature and then run gpg again
> % on that output to decrypt the msg.  Why is that happening?  Below
> 
> That's certainly a good question.  My guess at the moment is that it's an
> in-line encryption that has been MIME signed -- an interesting way to mix
> PGP processing.
> 
> 
> % is the from the mime messages which I can't read..
> % 
> ...
> % [-- PGP output follows (current time: Tue Jul 16 17:11:22 2002) --]             
> 
> This is good...
> 
> 
> ...
> % [-- End of PGP output --]                                                       
> 
> That's the end of that PGP report and we've now stripped away the
> signature.
> 
> 
> %                                                                                 
> % [-- BEGIN PGP SIGNED MESSAGE --]                                                
> 
> Now we see what was sent.
> 
> 
> %                                                                                 
> ...
> % -----BEGIN PGP MESSAGE-----                                                     
> % Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>          
> 
> Oho!  This looks traditional!  Hence my thoughts of the mixing.
> 
> What about starting simply: can you send yourself signed, encrypted, and
> signed+encrypted messages and read them properly?
> 
> If *you* can read *your* messages, then whose can you not read?  Is it
> just one person?  Put your public key on the servers and we can try
> sending you (signed and unsigned) encrypted messages for you to test.
> 

I can read my messages fine with no problem. My key should be on
the public servers. I uploaded it to wwwkeys.nl.pgp.net a couple
of months ago.
Since this is the only person I communicate with using encryption at
the moment I have had no one else to compare it with. They are
using Eudura/Windows with the PGPfreeware 7.0.3 plugin.

> Have one of your problematic correspondents send you vanilla test
> messages in s+e and u+e formats so that you can attach them for the list
> so that we have a real example to view.  We don't need your private key
> (or even the other person's public key); we just need the actual email.
> Hmmm...  In fact, it doesn't matter what's in the message, does it? :-)
> 
I have attached one of the problem msgs <file testmsg.pgp>. Let me know
what you find out.

TIA

jbw


> 
> ...
> % 
> % 
> % Is this a problem with mutt or gpg?
> 
> It looks to me like a problem with the sender and perhaps his MUA's
> configuration, actually.
> 
> 
> % 
> % TIA
> % 
> % jbw
> 
> 
> HTH & HAND
> 
> :-D
> -- 
> David T-G                      * It's easier to fight for one's principles
> (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
> (work) [EMAIL PROTECTED]
> http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
> 


Attachment: testmsg.pgp
Description: PGP message

Attachment: msg29734/pgp00000.pgp
Description: PGP signature

Reply via email to