Hi! 👋
I've stumbled upon what seems to a timing issue within the PicoKeys firmware.
From what I can understand, it appears that there is some kind of issue with the PicoKeys firmware wherein it doesn't react to the CTAPHID_INIT command of libfido2 early enough (or at all), causing libfido2 to wait indefinitely, which in turn prevents LUKS2-encrypted computers from ever powering on.
The solution I've found was to replug the PicoKey.
I have tried this with the following hardware and software, and have therefore concluded that this is a firmware issue:
- Waveshare RP2040-One, pico-fido2 6.6.0
- Waveshare RP2350-One, pico-fido2 6.6.0
- Raspberry Pi Pico 2, pico-fido2 6.6.0
I previously commented about this within the libfido2 issue tracker: Yubico/libfido2#852 (comment)
Any ideas?
Kind regards
Hi! 👋
I've stumbled upon what seems to a timing issue within the PicoKeys firmware.
From what I can understand, it appears that there is some kind of issue with the PicoKeys firmware wherein it doesn't react to the
CTAPHID_INITcommand of libfido2 early enough (or at all), causing libfido2 to wait indefinitely, which in turn prevents LUKS2-encrypted computers from ever powering on.The solution I've found was to replug the PicoKey.
I have tried this with the following hardware and software, and have therefore concluded that this is a firmware issue:
I previously commented about this within the libfido2 issue tracker: Yubico/libfido2#852 (comment)
Any ideas?
Kind regards