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 335514 - Integrate key creation, gpg --recv-key and gpg --sign-key in evolution's ui
Integrate key creation, gpg --recv-key and gpg --sign-key in evolution's ui
Status: RESOLVED DUPLICATE of bug 217269
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-03-22 13:23 UTC by surak
Modified: 2006-03-22 23:49 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description surak 2006-03-22 13:23:34 UTC 
You receive a signed email. You know this email is from someone you trust and
that the contents have not changed while in transit (say this people called you).

But there's an awful red stripe saying "INVALID SIGNATURE". When you click it, a
even more criptic (for noobs) warning saying that this message could not be
verified and could have changed while in transit (what is not exactly true).

What I propose is that we give the user means to

- create your own gpg key and send it to a trusted keyserver
- receive gpg keys from a default trusted keyserver (whatever it is -
pgp.mit.edu or whatever)
- sign received keys

WITHOUT leaving evolution to command line.

This would simplify A LOT the process of signature, which is not easy for everyone.
Comment 1 André Klapper 2006-03-22 23:49:26 UTC 
Thanks for the bug report.
You do not need to leave to the command line, you can just use an application to manage your gpg keys, like seahorse or kgpg or whatever...

Anyway, 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 217269 ***