Created attachment 635081 [details] Patch to fix fedora-burn-yubikey call to ykpersonalize (adds "-1" argument). Description of problem: /usr/sbin/fedora-burn-yubikey is not compatible with ykpers-1.8.0 and current yubikeys (an extra argument to /usr/bin/ykpersonalize is required). Version-Release number of selected component (if applicable): fedora-packager-0.5.10 Steps to Reproduce: 1. Run fedora-burn-yubikey and enter requested information. Actual results: Error message: ----- New key generated in FAS, attempting to burn to yubikey Firmware version 2.2.3 Touch level 1793 Program sequence 2 A slot must be chosen with -1 or -2. There was an error writing to your yubi key ----- Note that the error message ("A slot must be chosen...") is actually coming from /usr/bin/ykpersonalize. Expected results: The yubikey would burn successfully. Additional info: The attached patch adds the required argument.
I've also encountered this problem just now. I'll try the patch later, hopefully that will work, thanks Chris!
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.