Issues that do not require touch #255

Closed
opened 2026-02-06 08:59:30 +08:00 by 0x16ff · 1 comment
0x16ff commented 2026-02-06 08:59:30 +08:00 (Migrated from github.com)

when using firmware v6.6, entering a pin on the authentication website would prompt for a touch, and only after touching could one proceed. However, with v7.4, entering a pin directly grants access without the need for any touch operation. Is this normal?

The firmware is built from source code without using the picoKey app for configuration. Here is my build command: PICO_SDK_PATH=/pico-sdk-path cmake .. -DPICO_BOARD=pico2 -DVIDPID=Yubikey5

when using firmware v6.6, entering a pin on the authentication website would prompt for a touch, and only after touching could one proceed. However, with v7.4, entering a pin directly grants access without the need for any touch operation. Is this normal? The firmware is built from source code without using the picoKey app for configuration. Here is my build command: PICO_SDK_PATH=/pico-sdk-path cmake .. -DPICO_BOARD=pico2 -DVIDPID=Yubikey5
0x16ff commented 2026-02-07 08:01:31 +08:00 (Migrated from github.com)

I have seen the modifications submitted this time. Apart from modifying the source code, how can I change the value of button_timeout during firmware compilation?

7e6e3c8f3c...08dc94a144 (diff-e0cf5b28d9b6b600f0af2bc78e8fd30ec675fd731a5da86f0c4283ffc0e40176)

I have seen the modifications submitted this time. Apart from modifying the source code, how can I change the value of button_timeout during firmware compilation? https://github.com/polhenarejos/pico-keys-sdk/compare/7e6e3c8f3c7d4f7e9aa5f7f94de4a3560fbf59cb...08dc94a144b4a7a4f1207052df26b28b0399c8c9#diff-e0cf5b28d9b6b600f0af2bc78e8fd30ec675fd731a5da86f0c4283ffc0e40176
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#255