The Yubico OTP feature is not working on the ESP32-S3 with the new Version 7.0. #208
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?
I have two ESP32-S3 devices: one is running an unupgraded Version 6.6, and the other is on Version 7.0.
After testing, Yubico OTP functionality works normally on Version 6.6. However, on Version 7.0 (both the official stable release and Nightly Stable builds), it is unusable, and the BOOT button is unresponsive.
Please provide steps to reproduce it.
Step 1: In esp32-flasher, select Pico Fido and flash it to ESP32-S3.
Step 2: Then, in pico-commissioner, select the following:
After successful configuration, unplug and replug the device.
Step 3: In yubico-authenticator, select "Slots," click "Short touch," and then set a "Static password." After successful setup,
Step 4: When trying to use "Short touch" in a text document, a single click of the BOOT button produces no input.
I still have problems with the new firmware (Challenge-response) and a Waveshare ESP32-S3 Mini Development Board. Is there a way to go back or could one be integrated into /esp32-flasher/.
It mostly worked (I had to click a button three times) with the old firmware and KeePassXC. With the new Firmware, it only worked once.
Cannot reproduce neither in a RP2040 nor in a ESP32.
I am new to this so I hope I don't waste anyone's time... With the new Firmware it takes 25-35 seconds for me till I can use the key in KeePassXC.
If I press the button before that time, the key will be available just for a millisecond and immediately will be not shown anymore as an option in KeePassXC.
With the old Firmware, if I would press the button ~three times the key would be immediately available towards KeePassXC.
Got another one of those, same problem. But it looks to be specific to KeepassXC. I configured "Static Password" and it works immediately in notepad but takes again almost 40 seconds until it can be used in KeePassXC.
KeepassXC is doing a detection operation (fake challenge-response) according to droidmonkey, which explains the almost 40 seconds wait time I guess, the Pico Key is working fine after that.