Challenge-Response settings are not working properly #123
Reference in New Issue
Block a user
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?
Waveshare 2350 one, version 6.4, the challenge response setting requires touch, but in actual use it passes without touching. Flashing pico2 version 6.4 also has the same problem
It never worked under rp2040 either! I'm deaf to this error!
https://github.com/polhenarejos/pico-fido/issues/104
Tested on KeePassXC, thanks for the quick fix
I also encountered this problem.
I want to ask, if I re-flash a new firmware, will the previously saved keys be cleared?
If you reflash with the same firmware, nothing will change. Keys are preserved until the board is nuked.
I tried the new firmware, but KeePassXC on Arch Linux still can't find the hardware key. However, KeePassXC on Windows can find it. Where did I go wrong?
slot1 and slot2 have content and you turn on require touch to fit in. When you touch touch, nothing happens, only the challenge response is there, so this has not been fixed yet!
https://ibb.co/hRKp8xnf
Did you change the Product Name?
I set the Product Name to yubico yubikey.
Keepassxc on Windows recognizes it normally.
Yubico YubiKey can also be seen in Device Manager.
Use latest nightly development build. Yesterday I pushed a fix.
Problem solved, thanks for the development work!
If you turn on Challenge-Response, touch does not work in slot1 and slot2 swap mode, there are still bugs in the development version!
There is another problem. When the static password is set, setting and deleting the password for the slot does not affect the setting. However, whether you set the challenge first and then the password, or set the password first, set the challenge and then delete the password, it will cause verification to fail.
I'm not getting the point. Can you describe step by step the problem to reproduce it? The better with ykman.
To put it simply, as long as the otp is set to challenge the password attribute of the modified slot, the challenge data will be damaged and the challenge verification will fail.
For example, after setting the challenge, setting the password through the ykman otp settings -A 576bc54882f3 2 command will cause the challenge verification to fail.