Description of problem: Current Google-Authenticator is based on a git snapshot almost a year old. Upstream has since release version 1.0 which includes several features not present in this older snapshot, such as nullok on the pam module, HMAC code based one-time-passcodes, and command line options on google-authenticator. Version-Release number of selected component (if applicable): Current version in Fedora 16: google-authenticator-0-0.2.20110830 Current version in Fedora 17: google-authenticator-0-0.3.20110830 Current version in Rawhide: google-authenticator-0-0.4.20110830 Current version from Google itself: 1.0. https://google-authenticator.googlecode.com/files/libpam-google-authenticator-1.0-source.tar.bz2 Please rebase to the latest source. Related: https://bugzilla.redhat.com/show_bug.cgi?id=754978
Please make sure you use the proper PAM formatting (i.e. pam_google_authenticator). As explained into previous tickets, root based security should be enforced. Have a look at my tutorial and how I outlined the package for Redhat/CentOS 5 and 6: http://www.axivo.com/go/googleauth Regards, Floren Munteanu
Related: https://bugzilla.redhat.com/show_bug.cgi?id=850949
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.
This is still true for F18: google-authenticator-0-0.4.20110830.hgd525a9bab875.fc18 but not for F19: google-authenticator-1.0-0.gita096a62.fc19.1
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.