-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OATH read code APDUError #358
Comments
I'm relieved you were able to recover from the situation, and thanks so much for the detailed information, it's already given us a few leads to investigate. Based on your experience, I believe something went wrong with adding the new credential, likely due to the nature of NFC being an unreliable channel. We'll do some experimentation to see if we can reproduce this internally, and see how to best improve our apps to handle this situation. Again, showing that it's something we can recover from (at least in your specific case) means there is definite room for improvement here! |
Same problem. Happened on a botched credential add via NFC. Same solution. |
Seeing same issue:
I removed what looked liked a corrupted account, I don't want to remove any of the others but I can't generate codes for anything either. Any suggestions on how to get past this? |
Steps to reproduce
The Yubikey worked well until now.
Today after doing a write OATH using Yubico Authenticator android app with NFC the Yubikey OATH feature stopped working.
The android app shows "error in Yubikey communication".
I attached the Yubikey to the mac and used
ykman oath list
it shows my OTP list but if I try to launchykman oath code
it throws an APDUError:Does this error mean that I've lost all my secrets?
I should send my Yubikey back for a warranty repair?
UPDATE
I've been able to make it work again deleting the new entry with
ykman oath delete <MY NEW OTP>
Maybe this should be handled better or documented as a recovery method
The text was updated successfully, but these errors were encountered: