dearsky/pico-fido
1
0
Fork 0
Code Issues 46 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

Challenge Response Failed to connect #19

New Issue
Closed
opened 2023-10-22 01:42:10 +08:00 by 641i130 · 6 comments
641i130 commented 2023-10-22 01:42:10 +08:00 (Migrated from github.com)
Copy Link

Using ykman in this reddit post:
https://www.reddit.com/r/KeePass/comments/opx34q/keepassxc_and_yubikeys_setting_up_the/
I'm getting the follow response from the device:

# ykman otp chalresp -t -g 2
Using a randomly generated key (hex): 4e613cf377db2a67bfeebe9ba8b70d99f90daa99
Program a challenge-response credential in slot 2? [y/N]: y
ERROR: Failed to write to the YubiKey. Make sure the device does not have restricted access (see "ykman otp --help" for more info).

I'm using a Xiao Seeed if it matters.

Using `ykman` in this reddit post: https://www.reddit.com/r/KeePass/comments/opx34q/keepassxc_and_yubikeys_setting_up_the/ I'm getting the follow response from the device: ```bash # ykman otp chalresp -t -g 2 Using a randomly generated key (hex): 4e613cf377db2a67bfeebe9ba8b70d99f90daa99 Program a challenge-response credential in slot 2? [y/N]: y ERROR: Failed to write to the YubiKey. Make sure the device does not have restricted access (see "ykman otp --help" for more info). ``` I'm using a Xiao Seeed if it matters.
polhenarejos commented 2023-10-24 23:26:25 +08:00 (Migrated from github.com)
Copy Link

Actually, the error comes from the same as in #12: Windows is not able to HID GET FEATURE. But whilst in #12 ykman is able to fallback to another backend, this is not the case for OTP, which only uses HID FEATURE report backend. I cannot figure out how to make it work in windows.

Actually, the error comes from the same as in #12: Windows is not able to HID GET FEATURE. But whilst in #12 ykman is able to fallback to another backend, this is not the case for OTP, which only uses HID FEATURE report backend. I cannot figure out how to make it work in windows.
👀 1
641i130 commented 2023-10-31 08:21:45 +08:00 (Migrated from github.com)
Copy Link

With the development pull and the updated pico-hsm-sdk, I'm able to get it to generate, but keepassxc doesn't seem to see it yet oddly.
image
image

Heres what it should look like:
image

I'd like to help debug this, but I'm not sure what information is needed. Maybe USB pcap?

With the development pull and the updated `pico-hsm-sdk`, I'm able to get it to generate, but [keepassxc](https://keepassxc.org/) doesn't seem to see it yet oddly. ![image](https://github.com/polhenarejos/pico-fido/assets/46945263/a6389fac-0ec1-42da-87d6-0fcf96f187cd) ![image](https://github.com/polhenarejos/pico-fido/assets/46945263/51aa0235-1135-45c3-befb-98f0bf08bfd3) Heres what it should look like: ![image](https://github.com/polhenarejos/pico-fido/assets/46945263/f1ebed44-cb71-4716-a957-9d01f89d598f) I'd like to help debug this, but I'm not sure what information is needed. Maybe USB pcap?
polhenarejos commented 2023-10-31 16:24:11 +08:00 (Migrated from github.com)
Copy Link

Which OS?

Which OS?
641i130 commented 2023-10-31 23:46:27 +08:00 (Migrated from github.com)
Copy Link

Arch Linux

Arch Linux
polhenarejos commented 2023-11-01 00:37:59 +08:00 (Migrated from github.com)
Copy Link

Fixed in e5d1ef2.

Do not forget to pull sdk too. It works with KeepassXC when a slot is properly configured with Challenge-response credential type (via Yubikey Manager for instance.

Fixed in e5d1ef2. Do not forget to pull sdk too. It works with KeepassXC when a slot is properly configured with Challenge-response credential type (via Yubikey Manager for instance.
641i130 commented 2023-11-01 09:03:44 +08:00 (Migrated from github.com)
Copy Link

It works! Thank you so much for making this project. It's very interesting to me, someone getting into embedded systems design! I also like that we can make our own keys instead of buying them all from Yubico!!!

It works! Thank you so much for making this project. It's very interesting to me, someone getting into embedded systems design! I also like that we can make our own keys instead of buying them all from Yubico!!!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#19
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?