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 795124 - valid gpg signed message shows warning address and signer address do not match
valid gpg signed message shows warning address and signer address do not match
Status: RESOLVED DUPLICATE of bug 792610
Product: evolution
Classification: Applications
Component: Mailer
3.26.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2018-04-10 08:52 UTC by Benjamin
Modified: 2018-04-10 14:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Benjamin 2018-04-10 08:52:30 UTC
A valid gpg signed message shows a warning: Valid signature, but sender address and signer address do not match.

I have a gpg key with multiple aliases (e-mail addresses). Only sent (&signed) by the main e-mail shows a green sign in evolution. Sent and signed from my aliases shows a warning. Even in Evolution of the recipient.
With Thunderbird and Enigmail it is all fine (valid).

If I click on the warning button it shows that all is valid.

My Keys are ultimately trusted.

seems to be this:
https://github.com/GNOME/evolution/blob/master/src/em-format/e-mail-formatter-secure-button.c#L50

My key:
https://keybase.io/bpereto/pgp_keys.asc

regards,
Comment 1 Milan Crha 2018-04-10 14:23:09 UTC
Thanks for a bug report. The trust level is fine and when it's so evolution also checks whether the sender and key addresses match. The problem is that gpg returns only the main address, the aliases are returned in a free form string, which you might see in the dialog, which is shown when you click the warning button in the evolution.

This had been fixed in bug #792610, which is part of 3.28.0 release. There had been filled also bug #794501, which you may or may not be affected too. As you use 3.26.x, I'm closing this as a duplicate of the former bug report.

*** This bug has been marked as a duplicate of bug 792610 ***