dearsky/pico-fido
1
0
Fork 0
Code Issues 46 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

Version 6.4 Fails to Take Effect in pico-commissioner #120

New Issue
Closed
opened 2025-03-16 09:10:41 +08:00 by GN998 · 8 comments
GN998 commented 2025-03-16 09:10:41 +08:00 (Migrated from github.com)
Copy Link

First of all, thank you! Your project is truly excellent!

pico_fido_waveshare_rp2350_one-6.4.uf2
I've tried using Version 6.4 of pico-commissioner, but the configuration fails to take effect. Commission via WebAuthn cannot be debugged successfully, while Nightly Development functions without issue.

First of all, thank you! Your project is truly excellent! pico_fido_waveshare_rp2350_one-6.4.uf2 I've tried using Version 6.4 of pico-commissioner, but the configuration fails to take effect. Commission via WebAuthn cannot be debugged successfully, while Nightly Development functions without issue.
polhenarejos commented 2025-03-17 18:17:10 +08:00 (Migrated from github.com)
Copy Link

Yes, you are right. Latest enhancements in the development branch broke Pico Commissioner for stable version. I'd recommend you to use the development nightly build. It seems pretty stable and works with the Commissioner.

I hope to release a new version on Wed.

Yes, you are right. Latest enhancements in the development branch broke Pico Commissioner for stable version. I'd recommend you to use the development nightly build. It seems pretty stable and works with the Commissioner. I hope to release a new version on Wed.
👍 1
GN998 commented 2025-03-17 23:03:01 +08:00 (Migrated from github.com)
Copy Link

Thank you for your reply!

Both Nightly Stable and Version 6.4 exhibit the same issue. Nightly Development appears to be functioning normally. I look forward to subsequent releases.

However, I've encountered a recent problem with pico-commissioner. After flashing the firmware, when enabling Secure Boot and Secure Lock, should I select as shown in the image, or should I still enter the boot menu and select as shown in the image?

Image

I've attempted both methods, but neither works after entering the boot menu! Furthermore, I'm unable to successfully debug "Commission via WebUSB" using the Edge browser on win11_24H2. Although Edge on my Android system indicates success, my Ubuntu 22.4 virtual machine shows no response at all. Please investigate this situation!

Thank you for your reply! Both Nightly Stable and Version 6.4 exhibit the same issue. Nightly Development appears to be functioning normally. I look forward to subsequent releases. However, I've encountered a recent problem with pico-commissioner. After flashing the firmware, when enabling Secure Boot and Secure Lock, should I select as shown in the image, or should I still enter the boot menu and select as shown in the image? ![Image](https://github.com/user-attachments/assets/3935889b-9f97-4349-827f-ed0d1df1fa8d) I've attempted both methods, but neither works after entering the boot menu! Furthermore, I'm unable to successfully debug "Commission via WebUSB" using the Edge browser on win11_24H2. Although Edge on my Android system indicates success, my Ubuntu 22.4 virtual machine shows no response at all. Please investigate this situation!
polhenarejos commented 2025-03-17 23:12:26 +08:00 (Migrated from github.com)
Copy Link

What do you mean by "debugging"? Pico Commissioner is for commissioning Pico Keys, not for debugging.

What do you mean by "debugging"? Pico Commissioner is for commissioning Pico Keys, not for debugging.
😆 1
GN998 commented 2025-03-17 23:25:12 +08:00 (Migrated from github.com)
Copy Link

Apologies, my description was incorrect, and I have corrected it above.

What I meant to convey is that upon clicking "Commission via WebUSB", Android indicates success, while both the Edge browser on win11 and the Firefox browser on Ubuntu 22.04 show absolutely no response.

Furthermore, this bug prevents me from confirming whether "Secure Boot and Secure Lock" have been enabled. I'd like to know how to detect or verify if Secure Boot and Secure Lock are indeed activated.

Apologies, my description was incorrect, and I have corrected it above. What I meant to convey is that upon clicking "Commission via WebUSB", Android indicates success, while both the Edge browser on win11 and the Firefox browser on Ubuntu 22.04 show absolutely no response. Furthermore, this bug prevents me from confirming whether "Secure Boot and Secure Lock" have been enabled. I'd like to know how to detect or verify if Secure Boot and Secure Lock are indeed activated.
polhenarejos commented 2025-03-18 03:07:03 +08:00 (Migrated from github.com)
Copy Link

Firefox does not support WebUSB. Edge should work since 80.

My recommendation is using a Chromium-based browser.

For the record: I tried with Edge 134 and it doesn't work. It seems USB drivers must be replaced with Zadig, start edge with webUSB enabled and modify group policy to disable usb access prohibition. Tipical from Windows.

Firefox does not support WebUSB. Edge should work since 80. My recommendation is using a Chromium-based browser. For the record: I tried with Edge 134 and it doesn't work. It seems USB drivers must be replaced with Zadig, start edge with webUSB enabled and modify group policy to disable usb access prohibition. Tipical from Windows.
👍 1
GN998 commented 2025-03-19 12:29:46 +08:00 (Migrated from github.com)
Copy Link

Thank you for your effort.

Thank you for your effort.
Docteh commented 2025-05-19 14:19:35 +08:00 (Migrated from github.com)
Copy Link

It seems USB drivers must be replaced with Zadig, start edge with webUSB

Ya, just tried setting this up, with Chrome 136 and Edge 136, and the commissioning page didn't give any errors at all, but only got anywhere after I found the comment here to try zadig to assign a driver. I think it should be mentioned somewhere.

Can I assign a different vendor ID/product name after enrolling a passkey with a website like github?

> It seems USB drivers must be replaced with Zadig, start edge with webUSB Ya, just tried setting this up, with Chrome 136 and Edge 136, and the commissioning page didn't give any errors at all, but only got anywhere after I found the comment here to try zadig to assign a driver. I think it should be mentioned somewhere. Can I assign a different vendor ID/product name after enrolling a passkey with a website like github?
polhenarejos commented 2025-05-19 14:41:48 +08:00 (Migrated from github.com)
Copy Link

Which driver you assigned?
WebAuthn commissioning should work without zadig though.

I didn’t try it, but it should work as the credential is not related with vidpid.

Which driver you assigned? WebAuthn commissioning should work without zadig though. I didn’t try it, but it should work as the credential is not related with vidpid.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#120
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?