Re: [Evolution] Sometimes can't verify signature



On Sat, 2020-05-09 at 21:39 +0200, Ángel wrote:
On 2020-05-08 at 00:49 -0400, Jeff Van Epps via evolution-list wrote:
Evolution is able to verify the gpg signature on some messages but
on
other messages it says "Error verifying signature: Failed to
execute
gpg."

Is it failing consistently on certain messages, or is it sometimes
failing but maybe working for that exact message on the next attempt?


 I have not been able to get it to tell me any details about the
error. When I run

CAMEL_DEBUG=all evolution > foo.txt

the resulting file does not contain "gpg", "Error verifying
signature",
or "Failed to execute gpg". It does contain "GNUPG" in two places
which
both only say

status: [GNUPG:] NODATA 4

Is there a way to get it to output the actual gpg command it is
executing and the output from that command?

Also, I don't see a way to export the signature, just to help me
investigate (no attachment bar or anything). Is there one?
(FYI: Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature"; )

You may do Ctrl+U to view the message source (or just save as mbox)

I have debugged this kind of things in the past by placing a wrapper
around gpg earlier in the PATH, which logs how/what is being passed
around.

I created ~/bin/gpg2

#!/bin/bash

echo $* > /home/lordbah/args.txt

What appears in args.txt is:

--verbose --no-secmem-warning --no-greeting --no-tty --batch --yes --
status-fd=85 --verify-options show-photos --photo-viewer
/usr/libexec/camel-gpg-photo-saver --state "/tmp/camel-gpg-photo-state-
WDV3J0" --photo "%i" --keyid "%K" --type "%t" --verify /tmp/evolution-
pgp.FCM3J0 -

However ... 
- the same stuff appears for both kinds of messages, those whose
signature can be verified and those whose can't
- there is no /tmp/camel* file while this is being executed
- none of those are documented options for gpg2 except --verify and --
verbose!
- I don't know what those percent variables are doing

So I'm kind of bewildered by all this. It's as if evolution is
expecting to run some program other than gpg.

Hmm, the "bad" message has both a text/plain part and a text/html part,
wherease the "good" message has only a text/plain. I wonder if that's
an issue.

gpg version is 2.2.12.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]