Re: [Evolution] Problem reading PGP encrypted message

[Patrick O'Callaghan <poc usb ve>]

On 11/4/10 4:29 PM, pablo a saavedra gmail com wrote:
> On 4 November 2010 17:50, Patrick O'Callaghan <poc usb ve 
> <mailto:poc usb ve>> wrote:
>
>     On 11/4/10 3:33 PM, pablo a saavedra gmail com
>     <mailto:pablo a saavedra gmail com> wrote:
>
>
>
>         On 4 November 2010 16:56, Patrick O'Callaghan <poc usb ve
>         <mailto:poc usb ve> <mailto:poc usb ve <mailto:poc usb ve>>>
>         wrote:
>
>            [Please don't top-post on this list]
>
>
>            On 11/4/10 2:08 PM, pablo a saavedra gmail com
>         <mailto:pablo a saavedra gmail com>
>         <mailto:pablo a saavedra gmail com
>         <mailto:pablo a saavedra gmail com>> wrote:
>
>                Hi Patrick, the problem is that I only see the two
>         attachments
>                (both .asc), not the email text. Sorry if I didn't express
>                myself correctly, he has my public key and I have his, we
>                already verified that signing works OK (both see our valid
>                signatures in the messages).
>
>
>            Some details are still missing. Is your co-worker encrypting,
>            signing, or both? Is he using PGP or S/Mime? What error
>         message is
>            Evo showing when you try to open the message?
>
>            poc
>
>
>         We tried both encrypting without signing and encrypting and
>         signing. We are using PGP, we generated our signatures using
>         Gnome's password and encryption keys application. There's no
>         error message, just the message with both attachments as I
>         mentioned.
>
>
>     How about signing without encrypting? Have you tried running the
>     received files through gpg on the command-line?
>
>     poc
>
>
> Just signing works great. I'll try running them through the command 
> line and let you know how it works. But what should the behavior on 
> this case?
GPG should just verify the signature and/or decrypt the message, 
depending on the use case. Evo is just acting as a front-end, so if 
there's a problem it's likely to be the GPG setup rather than Evo. Of 
course you have to check that Evo is using the correct GPG keys for 
encryption and verification, i.e. it has access to the keyring.

poc

poc