+++ This bug was initially created as a clone of Bug #498926 +++ Description of problem: I have just gave a try the new fingerprint support in upcoming Fedora 11 and after installing gdm-plugin-fingerprint to enable the fingerprint authentication everything seemed to be ok. However, after authentication with my fingerprint scanner, NetworkManager asked me for my password to unlock the default keyring so I still had to type in my password. Version-Release number of selected component (if applicable): gdm-plugin-fingerprint 1:2.26.1-4.x86_64 How reproducible: Always Steps to Reproduce: 1. Install gdm-plugin-fingerprint package and setup your fingerprint authentication in the user info tool. 2. Logout 3. Login using your fingerprint scanner. Actual results: Default keyring still requires to type in user password. Expected results: Once authenticated in GDM with the fingerprint scanner default keyring should be unlocked as well - like it is with regular password authentication. Additional info: --- Additional comment from mclasen on 2009-05-04 12:22:22 EDT --- That is not an easy thing to do, since the keyring is locked with your password. If you don't enter your password, it is not available for unlocking the keyring. Same thing with automatic login. --- Additional comment from dzrudy on 2009-05-04 12:58:18 EDT --- Uh ok, I guess that GNOME would need to implement unlocking the keyring via fingerprint in order to enable such support. AFAIK the current fingerprint authentication is implemented around PAM and PAM is not used for keyrings right? --- Additional comment from fedora.uk on 2009-05-18 18:43:48 EDT --- Presumably the keyring is *encrypted* with your password and therefore it is impossible to unlock the keyring by use of a fingerprint device. To make this work you'd have to forgo encryption of the keyring, which is probably not a great idea. --- Additional comment from triage.org on 2009-06-09 11:07:26 EDT --- This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping --- Additional comment from triage.org on 2010-04-27 10:06:47 EDT --- This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping --- Additional comment from liblit on 2010-04-27 12:05:13 EDT --- This is definitely still a problem under Fedora 12, but I do not have the power to update the "Version" field accordingly. Would someone please do that? Thanks! --- Additional comment from pobara on 2010-08-24 09:38:04 EDT --- This is still problem under Fedora 13, can Version field be updated again? Shouldn't status of this bug be ASSIGNED instead of NEW? --- Additional comment from dzrudy on 2010-08-24 10:14:29 EDT --- Patryk, I have just set the version to 13. --- Additional comment from mrlhwliberty on 2010-10-12 22:22:59 EDT --- The problem is still there in Fedora 14 --- Additional comment from hajo on 2011-03-08 05:54:05 EST --- It seems to be easy for Ubuntu, why not for Fedora: http://johnny.chadda.se/article/unlock-the-gnome-keyring-upon-login/ --- Additional comment from hajo on 2011-03-08 05:56:05 EST --- Apologies, my mistake. Should have been reading carefully before posting. Please ignore previous comment :( --- Additional comment from marbolangos on 2011-05-20 08:27:33 EDT --- Same in F15 (all updates done). --- Additional comment from rstrode on 2011-05-24 21:07:27 EDT --- This would be a useful feature but is sort of "hard" to implement. it would probably involve using the fingerprint hash as a key. Honestly, this would be better as upstream pam_fprint RFE. --- Additional comment from endoflife on 2012-08-16 14:07:09 EDT --- This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.