"Hardware key error: timeout" in KeepassXC #81

Closed
opened 2024-12-21 02:43:19 +08:00 by air-eat · 4 comments
air-eat commented 2024-12-21 02:43:19 +08:00 (Migrated from github.com)

KeepassXC can use a challenge-response slot in yubikeys as a replacement for passwords to decrypt databases (faq)

i set up a challenge-response credential in both slots in the pico fido using the yubikey manager (i spoofed a yubikey 5, and it did seem to save), but when i plug it in, KeepassXC says "Detecting hardware keys", then a second later spits out "Hardware key error: timeout" in the console (both in macOS and linux)

according to another issue, this means that the key was not touched in time, but i did not set touch to either of the slots, not did the key prompt me to touch it

KeepassXC can use a challenge-response slot in yubikeys as a replacement for passwords to decrypt databases ([faq](https://keepassxc.org/docs/#faq-yubikey-2fa)) i set up a challenge-response credential in both slots in the pico fido using the yubikey manager (i spoofed a yubikey 5, and it did seem to save), but when i plug it in, KeepassXC says "Detecting hardware keys", then a second later spits out "Hardware key error: timeout" in the console (both in macOS and linux) according to [another issue](https://github.com/keepassxreboot/keepassxc/issues/8853#issuecomment-1332838104), this means that the key was not touched in time, but i did not set touch to either of the slots, not did the key prompt me to touch it
polhenarejos commented 2024-12-21 03:01:50 +08:00 (Migrated from github.com)

Are you using the nightly development build?

Are you using the nightly development build?
air-eat commented 2024-12-21 03:14:21 +08:00 (Migrated from github.com)

yep, same behavior as 6.0
i also checked on windows, and that doesn't seem to even show up with the "Detecting hardware keys" text, but that sounds like it might be a different problem

yep, same behavior as 6.0 i also checked on windows, and that doesn't seem to even show up with the "Detecting hardware keys" text, but that sounds like it might be a different problem
air-eat commented 2024-12-22 23:56:47 +08:00 (Migrated from github.com)

i managed to get windows to work, but only if KeepassXC was started with a passkey already inserted; then it would work as intended, i could register it to a database, unlock a database with it, replug it and still have it detected, etc. if KeepassXC is started without a passkey inserted, it wouldn't detect it at all

again, this sounds like a different problem to linux/macOS

i managed to get windows to work, but only if KeepassXC was started with a passkey already inserted; then it would work as intended, i could register it to a database, unlock a database with it, replug it and still have it detected, etc. if KeepassXC is started without a passkey inserted, it wouldn't detect it at all again, this sounds like a different problem to linux/macOS
polhenarejos commented 2025-01-15 22:13:46 +08:00 (Migrated from github.com)

No activity. Reopen if needed.

No activity. Reopen if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#81