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 376412 - Feature Request: No UI for devices; no way to configure evolution to use smart cards from UI
Feature Request: No UI for devices; no way to configure evolution to use smar...
Status: RESOLVED DUPLICATE of bug 253574
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-11-17 18:54 UTC by Matthew Barnes
Modified: 2013-05-30 16:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthew Barnes 2006-11-17 18:54:43 UTC
Forwarding a feature request from downstream:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213918

Description of problem:
I have a smart card with my S/MIME certificates used for smart card login to
RHEL 5. I tried to use my smart card with evolution for signing and encrypting
email (S/MIME)  but there is no way from the UI to configure secure devices.

Version-Release number of selected component (if applicable):
RHEL5-Client-20061027.0 and 
evolution-data-server-1.8.0-13.el5
evolution-2.8.0-11.el5

How reproducible:
Always

Steps to Reproduce:
1. Insert your USB smart card to login
2. Start evolution 
3. 
  
Actual results:
There seems to be no way to configure evolution to use the certificates on the
smart card for use in signing and encrypting email. No way to configure devices
from the ui

Expected results:
There should be a way to configure devices from the UI

Additional info:
You can manually add the certs to the s/mime database from the command line and
they then do show up in the ui. However, they are still not useable. I'll file a
separate bug for that problem
Comment 1 Milan Crha 2013-05-30 16:17:10 UTC

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