Description of problem: fedora-burn-yubikey lets you pass -S 2 to set the second slot. However, if you read the ykpersonalize man page: -2 change the second configuration. This is for YubiKey II only and is then normally used for static key generation. In this configuration, the option flags -oappend-cr, -ostatic-ticket, -ostrong-pw1, -ostrong-pw2 and -oman-update are set by default. Needless to say, setting it up for a static key works very poorly in Fedora infrastructure. When using -2, you need to pass -o-static-ticket (and possibly -o-strong-pw1/-o-strong-pw2). Version-Release number of selected component (if applicable): fedora-packager-0.5.10.1-3.fc19.noarch How reproducible: 100% Steps to Reproduce: 1. try to use the second slot Actual results: Note that auth works... once. And then you get rejected with 'replayed OTP'. Expected results: Auth works with generated key sequences Additional info:
Odd. I am pretty sure we had this working and tested. ;( Adding nb here, as I think he worked on the script...
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
For some reason I never saw this bug. This was fixed in 0.5.10.3-1 I believe. Notting: can you please confirm that it works for you now?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days