🐛 WebAuthn Authentication Fails After Device Removal on pico-fido #110

Closed
opened 2025-02-14 02:15:19 +08:00 by afterow · 10 comments
afterow commented 2025-02-14 02:15:19 +08:00 (Migrated from github.com)

Description

After flashing pico-fido, the first WebAuthn authentication succeeds, but authentication fails after removing the device. Testing revealed that re-setting the PIN using Windows Hello miraculously restored WebAuthn authentication to normal.

Environment

  • Operating System: Windows 11
  • Firmware Version: esp32-s3_6.2
  • Browser: Chrome 133.0.6943.60
  • Chip Model: ESP32-S3 (QFN56)

Steps to Reproduce

  1. Flash pico-fido
  2. Bind the security key
  3. Remove the device
  4. WebAuthn authentication

Expected Behavior

Successful WebAuthn authentication.

Actual Behavior

Login fails.

Error Screenshot
### Description After flashing pico-fido, the first WebAuthn authentication succeeds, but authentication fails after removing the device. Testing revealed that re-setting the PIN using Windows Hello miraculously restored WebAuthn authentication to normal. ### Environment - Operating System: Windows 11 - Firmware Version: esp32-s3_6.2 - Browser: Chrome 133.0.6943.60 - Chip Model: ESP32-S3 (QFN56) ### Steps to Reproduce 1. Flash pico-fido 2. Bind the security key 3. Remove the device 4. WebAuthn authentication ### Expected Behavior Successful WebAuthn authentication. ### Actual Behavior Login fails. <img src="https://github.com/user-attachments/assets/69033266-b276-4d85-b002-05554645f063" alt="Error Screenshot" width="341" />
polhenarejos commented 2025-02-14 03:00:16 +08:00 (Migrated from github.com)

Can you flash the nightly development build?

Can you flash the nightly development build?
afterow commented 2025-02-14 03:07:37 +08:00 (Migrated from github.com)

I also flashed the nightly development build version, but the effect is the same.

I also flashed the nightly development build version, but the effect is the same.
afterow commented 2025-02-14 03:17:58 +08:00 (Migrated from github.com)

#91 I think my situation is the same as his

I believe this commit is the cause: commit 6a67800.

#91 I think my situation is the same as his I believe this commit is the cause: [commit 6a67800](https://github.com/polhenarejos/pico-fido/commit/6a678000570ccf95dbc67446a0fe4fdddfc5f28e).
polhenarejos commented 2025-02-14 03:56:01 +08:00 (Migrated from github.com)

But it is solved in the last development commit. Did you enrolled again the key after the development flash?

But it is solved in the last development commit. Did you enrolled again the key after the development flash?
afterow commented 2025-02-14 04:10:26 +08:00 (Migrated from github.com)

But it is solved in the last development commit. Did you enrolled again the key after the development flash?

Could you release a 6.2rc version? Your regular release versions do not have firmware for ESP32. I have tested nightly builds and other versions, but they do not work.

> But it is solved in the last development commit. Did you enrolled again the key after the development flash? Could you release a 6.2rc version? Your regular release versions do not have firmware for ESP32. I have tested nightly builds and other versions, but they do not work.
polhenarejos commented 2025-02-14 05:02:09 +08:00 (Migrated from github.com)

It’d the same as nightly builds.

This the last https://github.com/polhenarejos/pico-fido/releases/download/nightly-development/pico_fido_esp32-s3.bin

Be sure you register again the key in Windows hello. It will not work with the previous one.

It’d the same as nightly builds. This the last https://github.com/polhenarejos/pico-fido/releases/download/nightly-development/pico_fido_esp32-s3.bin Be sure you register again the key in Windows hello. It will not work with the previous one.
afterow commented 2025-02-14 05:30:24 +08:00 (Migrated from github.com)

I flashed the version you sent and it's still the same after unplugging it

Wait, I found something new. After entering the pin, you can log in normally.

Image

I flashed the version you sent and it's still the same after unplugging it Wait, I found something new. After entering the pin, you can log in normally. ![Image](https://github.com/user-attachments/assets/ba7d1aca-66e5-466f-8609-88768265288e)
polhenarejos commented 2025-02-18 01:17:17 +08:00 (Migrated from github.com)

I don't understand clearly the problem. Are you trying to register and login to Github or Windows?
Your key is PIN protected. So, it is normal that if you don't introduce the PIN it will not work. From the GIF you upload, I don't see Github asking you for a PIN.

I don't understand clearly the problem. Are you trying to register and login to Github or Windows? Your key is PIN protected. So, it is normal that if you don't introduce the PIN it will not work. From the GIF you upload, I don't see Github asking you for a PIN.
MiniProjectDIY commented 2025-03-07 17:38:23 +08:00 (Migrated from github.com)

I thinks this commit bdbdd92be8 fixed this issue,take a try.

I thinks this commit https://github.com/polhenarejos/pico-fido/commit/bdbdd92be8783d85aa12832b56f005dc1832c976 fixed this issue,take a try.
afterow commented 2025-03-07 19:20:47 +08:00 (Migrated from github.com)

This issue has been fixed in commit bdbdd92

This issue has been fixed in commit [bdbdd92](https://github.com/polhenarejos/pico-fido/commit/bdbdd92be8783d85aa12832b56f005dc1832c976)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#110