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 634105 - Wrong certificate used when signing & encrypting an e-mail
Wrong certificate used when signing & encrypting an e-mail
Status: RESOLVED DUPLICATE of bug 604534
Product: evolution
Classification: Applications
Component: general
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-11-05 18:03 UTC by nyyr1
Modified: 2011-01-19 11:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nyyr1 2010-11-05 18:03:06 UTC 
I have 2 certificates. One for signing and one for encrypting. When I just sign an e-mail, the right certificate is used (as selected in Settings-->Account-->Security tab). But when I sign AND encrypt an e-mail, the same certificate is used for signing and encrypting.
Comment 1 André Klapper 2010-11-08 21:04:22 UTC 
What kind of certificates?
Comment 2 nyyr1 2010-11-09 20:38:43 UTC 
My personal.
Comment 3 nyyr1 2010-11-12 08:50:57 UTC 
Oh my, I´m stupid !

".....the same certificate is used for signing and encrypting."

That´s nonsense of course :-) The correct desc. is that the encryption certificate is used for signing instead of the signing certificate (and the recipient´s cert. is used for encrypting :-) ).

I should also say that in the pulldown combo box of the certificate selection modal window both certificates have the same name (signKey #1) and I have to look at the text area below to see, which one I select (but when I open the selection modal window again, it shows the first? certificate info in the text area below  regardless of what certificate I selected the last time.
Comment 4 Milan Crha 2011-01-19 11:57:04 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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