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 741059 - Prompts for login PIN for PKCS#11 module with CKF_PROTECTED_AUTHENTICATION_PATH
Prompts for login PIN for PKCS#11 module with CKF_PROTECTED_AUTHENTICATION_PATH
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-12-03 09:57 UTC by David Woodhouse
Modified: 2014-12-08 14:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2014-12-03 09:57:52 UTC 
If a module sets CKF_PROTECTED_AUTHENTICATION_PATH in the flags returned from C_GetTokenInfo(), you're not supposed to prompt the user for a PIN for it. You're supposed to let *it* handle its own login. Perhaps it'll have a built-in keypad or something.

The GNOME Keyring module does this, because it's automatically unlocked at login time. But Evolution prompts for a PIN for it anyway.

On a modern Fedora system symlink /usr/lib64/libnssckbi.so to p11-kit-proxy.so (instead of p11-kit-trust.so). This will make p11-kit actually work properly and link in *all* the configured modules, and then you'll see that Evolution prompts for a PIN, while Firefox correctly doesn't.