After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 386471 - gpg encrypted message not decrypted when signature key not available
gpg encrypted message not decrypted when signature key not available
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[gpg]
: 531119 586745 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-16 11:51 UTC by Johannes Berg
Modified: 2021-05-19 12:11 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Johannes Berg 2006-12-16 11:51:59 UTC
Please describe the problem:
When you receive a message that is both encrypted and signed and try to view it, gpg is invoked to decrypt it but if the signature key is not present then the message is not shown even though it was decrypted properly.

Steps to reproduce:
1. Go to bug 386468 and get the test mail attached to it
2. import the test mail and the gpg key referenced there
2. delete my public key 9AB78CA5 from your keyring
3. view the test mail in evolution


Actual results:
lots of errors are displayed of which the last is the fact that the signature key is not known, no message is shown

Expected results:
message should be shown with a broken lock icon saying the signature could not be verified

Does this happen every time?
yes

Other information:
this can actually be quite important if the senders key isn't available from keyservers for some odd reason or if you're offline.

a workaround is to save the message and run it through gpg manually
Comment 1 Johannes Berg 2008-05-05 21:19:41 UTC
*** Bug 531119 has been marked as a duplicate of this bug. ***
Comment 2 David Ayers 2011-09-01 04:43:15 UTC
I can confirm this bug for Evolution Evolution 2.30.3
Comment 3 David Ayers 2011-09-02 17:01:23 UTC
I can add that is also an issue in Evolution 2.32.2

Note that if a message is signed & encrypted /by evolution/ then the message is decrypted and the icon and message are displayed about the missing public key to verify the signature.

Yet if the message is signed & encrypted /by Thunderbird/ the decryption dialog is shown and processed yet the contents are not rendered but displayed as attachments.
Comment 4 David Ayers 2011-11-08 06:54:13 UTC
This bug also affects Evolution 3.2 as distributed by Oneiric.
Comment 5 André Klapper 2012-01-24 20:57:51 UTC
*** Bug 586745 has been marked as a duplicate of this bug. ***
Comment 6 below 2012-02-24 11:24:04 UTC
Same problem here (Evolution 3.2.2, Debian testing): I have set GnuPG to fetch missing keys automatically. If the signature key isn't found on the keyserver, Evolution shows an error and doesn't decrypt the message. Other mail programs open the message fine. After adding the signature key to my public keyring, Evolution shows it without problems.
Comment 7 moritz.doll 2012-10-22 18:08:03 UTC
Also in Evolution 3.2.3.

Evolution output:

Could not parse PGP message: 
gpg: armor header: Version: GnuPG v2.0.19 (GNU/Linux)
gpg: public key is ********
gpg: public key is ********
gpg: using subkey ******** instead of primary key ********
gpg: using subkey ******** instead of primary key ********
gpg: public key is ********
gpg: encrypted with RSA key, ID ********
gpg: using subkey ******** instead of primary key ********
gpg: encrypted with 2048-bit RSA key, ID ********, created 2020-00-00
"foo@bar.baz"
gpg: AES256 encrypted data
gpg: original file name=''
gpg: Signature made Sun 21 Oct 2012 00:00:00 PM CEST using RSA key ID
********
gpg: Can't check signature: public key not found
Comment 8 quazgar 2012-10-22 18:26:24 UTC
Possibly a duplicate of the (even older!) bug #273856.
Comment 9 André Klapper 2021-05-19 12:11:57 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.