You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
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
The text was updated successfully, but these errors were encountered: