Skip to content
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

UX: Why not support for YubiKey NEO? #106

Closed
AnomalRoil opened this issue Jan 4, 2023 · 1 comment
Closed

UX: Why not support for YubiKey NEO? #106

AnomalRoil opened this issue Jan 4, 2023 · 1 comment

Comments

@AnomalRoil
Copy link

AnomalRoil commented Jan 4, 2023

What were you trying to do

Setting up an age key on my YubiKey Neo.

What happened

All want well until it asked me to touch the YK and failed (I've added the final response from my YK):

age-plugin-yubikey --generate --name 'YRO Yubi Neo - age'

Enter PIN for YubiKey with serial 4XXXXX8 (default is 123456): [hidden]
👆 Please touch the YubiKey
[TRACE yubikey::apdu] <<< Response { status_words: IncorrectSlotError, data: [] }
[ERROR yubikey::piv] failed to generate new key (incorrect slot)
Error: Error while communicating with YubiKey: key error

I finally found out here, that the YK Neo is not supported.
But it still has PIV support, so I was wondering why?
If it's just that it needed some customization and you didn't have one handy, I might be able to help.

@str4d
Copy link
Owner

str4d commented Jan 4, 2023

YubiKey NEO is not supported because it is unsupported by the upstream yubikey crate. See iqlusioninc/yubikey.rs#18 and iqlusioninc/yubikey.rs#63 for details. If yubikey regained support for NEO then age-plugin-yubikey likely would as well, but it's an upstream concern.

@str4d str4d closed this as completed Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants