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

Unable to create resident keys #3

Open
graystevens opened this issue Nov 23, 2021 · 7 comments · Fixed by #5
Open

Unable to create resident keys #3

graystevens opened this issue Nov 23, 2021 · 7 comments · Fixed by #5

Comments

@graystevens
Copy link

I've tried to generate a resident key on both of my Solo2s (USB-C and A) but both error out..

➜ ssh-keygen -t ed25519-sk -O resident -vvv
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter PIN for authenticator:
debug3: start_helper: started pid=18049
debug3: ssh_msg_send: type 5
debug3: ssh_msg_recv entering
debug1: start_helper: starting /opt/homebrew/Cellar/openssh/8.8p1/libexec/ssh-sk-helper
debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin
debug1: sshsk_enroll: using random challenge
debug1: sk_probe: 1 device(s) detected
debug1: sk_probe: selecting sk by touch
debug1: ssh_sk_enroll: using device IOService:/AppleARMPE/arm-io@10F00000/AppleT810xIO/usb-drd1@2280000/AppleT8103USBXHCI@01000000/usb-drd1-port-hs@01100000/Solo 2 Security Key@01100000/IOUSBHostInterface@1/AppleUserUSBHostHIDDevice
debug1: ssh_sk_enroll: IOService:/AppleARMPE/arm-io@10F00000/AppleT810xIO/usb-drd1@2280000/AppleT8103USBXHCI@01000000/usb-drd1-port-hs@01100000/Solo 2 Security Key@01100000/IOUSBHostInterface@1/AppleUserUSBHostHIDDevice does not support credprot, refusing to create unprotected resident/verify-required key
debug1: sshsk_enroll: provider "internal" failure -2
debug1: ssh-sk-helper: Enrollment failed: requested feature not supported
debug1: main: reply len 8
debug3: ssh_msg_send: type 5
debug1: client_converse: helper returned error -59
debug3: reap_helper: pid=18049
Key enrollment failed: requested feature not supported

Tried the same sequence on Ubuntu 20.04 and Arch machines (where I can successfully see them via solo2 and update them both). I've also run fido2-token, which provided the following:

➜ fido2-token -I /dev/hidraw4   
proto: 0x02
major: 0x00
minor: 0x00
build: 0x00
caps: 0x05 (wink, cbor, msg)
version strings: U2F_V2, FIDO_2_0
extension strings: hmac-secret
aaguid: xxxxxxxxxxxxxxxxxxxxxxxxx
options: rk, up, credMgmt, clientPin
maxmsgsiz: 7609
maxcredcntlst: 10
maxcredlen: 512
fwversion: 0x0
pin protocols: 1
pin retries: 8
uv retries: undefined
@nickray
Copy link
Member

nickray commented Nov 24, 2021

Ack.

@nickray nickray transferred this issue from solokeys/solo2-cli Nov 24, 2021
@nickray
Copy link
Member

nickray commented Nov 25, 2021

Fix incoming; ssh doesn't like us not signaling credProtect extension support in GetInfo.

@nickray
Copy link
Member

nickray commented Nov 26, 2021

Got auto-closed prematurely, will await the next release for feedback.

@graystevens
Copy link
Author

Have you got any rough timescales for when this may be included in a release? I'm keen to switch over from a few other keys, but this is blocking that unfortunately.

@nickray
Copy link
Member

nickray commented Feb 7, 2022

I think this particular PR should be in the latest released FW version 1.0.9, but I also can't full-heartedly recommend updating as there are other open issues still (some users claim ".7 works, but .8 and .9 do not").

@kanru

This comment was marked as duplicate.

@arathunku
Copy link

I'm running into the same issue.

I've set up PIN and key was generated but when doing "ssh-add -vvv -K", I get

debug1: read_rks: device /dev/hidraw6 does not support resident keys

I'm running on latest .09 version

robin-nitrokey added a commit to robin-nitrokey/fido-authenticator that referenced this issue Jun 28, 2023
Skip user presence check directly after boot
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

Successfully merging a pull request may close this issue.

4 participants