Latest upstream release: 1.11.0 Current version in Fedora Rawhide: 1.9.0 URL: http://code.google.com/p/yubikey-personalization/downloads/list Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 1.11.1 Current version in Fedora Rawhide: 1.9.0 URL: http://code.google.com/p/yubikey-personalization/downloads/list Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
production YubiKey NEO are shipping (I received mine yesterday) and it would seem 1.8.0 is too old to talk to this model. # rpm -qf `which ykpersonalize` ykpers-1.8.0-1.fc17.x86_64 # ykpersonalize -2 -ooath-hotp -ooath-imf=0 -ofixed= -oappend-cr -a<My secret> Yubikey core error: no yubikey present the key itself works (pressing the button gives a string back as expected) and I also successfully programmed a plain YubiKey a couple days ago on this box. Long story short; could you please build 1.11.1
Created attachment 672490 [details] patch to spec file to build 1.11.1 1.11.1 compiled just fine with the existing spec file two changes I made: - ykinfo is new, I put that in it's own sub-package. But it could also be in the main package. Your decision. - using %{_libdir}/libykpers-1.so.%{version} to avoid having to touch that part of the spec when the next update comes. Note, while I am @redhat.com, I'm not a developer. Just a fellow package maintainer in my spare time. :) Both ykinfo (on a F17 x86_64 box where I kept the old ykpers) and ykpersonalize (on the box I was testing earlier today) worked for my NEO.
Latest upstream release: 1.11.3 Current version in Fedora Rawhide: 1.9.0 URL: http://code.google.com/p/yubikey-personalization/downloads/list Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Created attachment 684109 [details] patch to spec file to build 1.11.3
with the patch from Comment #5 I was able to build and install 1.11.3 I did not do any changes to my YubiKeys with it though. Maxim: could you please push an update to F17, F18 and rawhide?
Latest upstream release: 1.12.0 Current version in Fedora Rawhide: 1.9.0 URL: http://code.google.com/p/yubikey-personalization/downloads/list Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Created attachment 710721 [details] patch to spec file to build 1.12.0 this replaces the patch from comment 5 This patch is against what's in Fedora git for ykpers today.
Any way we can get this packaged up and sent? I got my NEO in the mail today and I'm getting the same error: Yubikey core error: no yubikey present I build the 1.12.0 version from source but so far no luck.
ykpers-1.13.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ykpers-1.13.0-1.fc19
Package ykpers-1.13.0-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ykpers-1.13.0-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10057/ykpers-1.13.0-1.fc19 then log in and leave karma (feedback).
ykpers-1.13.0-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.