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
HI
I have the following issue:
usb-stick with keepass2.41 portable + keechallenge plugin
HMAC SHA1 on slot 1 (Fixed 64 byte input and require user input)
yubikey 5 NFC
keepass.kdbx with masterkey and keyfile: "Yubikey challenge-response"
PC1 win10 1809:
insert usb stick --> open keepass.kdbx --> enter masterkey --> press yubikey --> keepass.kdbx opened
PC2 win10 1803:
insert same usb-stick --> open keepass.kdbx --> enter masterkey --> Error "Error getting response from yubikey" --> can not open keepass.kdbx
On PC2:
I try ykchalresp -1 -t and get an response
I try yubico demo auth website --> everthing works
Can you help me to solve the issue?
The text was updated successfully, but these errors were encountered:
This issue occurs when you have the challenge response on slot 1, but what happens in KeePass is, the slot resets. So if you selected slot 1 initially, when you restart, it gets reset to slot 2. You can change this simply by going to Tools -> KeeChallenge Settings -> Slot 1, then it should work again.
Obviously my response is a bit late for you two, but I hope it might help people in the future.
HI
I have the following issue:
usb-stick with keepass2.41 portable + keechallenge plugin
HMAC SHA1 on slot 1 (Fixed 64 byte input and require user input)
yubikey 5 NFC
keepass.kdbx with masterkey and keyfile: "Yubikey challenge-response"
PC1 win10 1809:
insert usb stick --> open keepass.kdbx --> enter masterkey --> press yubikey --> keepass.kdbx opened
PC2 win10 1803:
insert same usb-stick --> open keepass.kdbx --> enter masterkey --> Error "Error getting response from yubikey" --> can not open keepass.kdbx
On PC2:
I try ykchalresp -1 -t and get an response
I try yubico demo auth website --> everthing works
Can you help me to solve the issue?
The text was updated successfully, but these errors were encountered: