USB Vendor ID / Product ID usage #242

New Issue

2026-01-06T04:28:39+08:00

mimi89999 commented

2026-01-06 04:28:39 +08:00

(Migrated from github.com)

Hello,

Thank you for your work on this project! I'm developing the Authnkey Android app and I've been testing with PICO FIDO.

I noticed that the project is using an unassigned USB Vendor ID (VID) and Product ID (PID) combination. In my app, I use VIDs to identify FIDO devices, and the unassigned VID/PID is causing issues with proper device identification.

Would it be possible to consider using a properly assigned VID/PID? For open-source projects, there are a few options:

pid.codes - Free PIDs for open-source projects
OpenMoko - Allocates PIDs under their VID for open-source projects
Raspberry Pi - Has a PID allocation program for projects using RP2040/RP2350: https://github.com/raspberrypi/usb-pid

Thanks again for this project!

Best regards,
Michel

Hello, Thank you for your work on this project! I'm developing the Authnkey Android app and I've been testing with PICO FIDO. I noticed that the project is using an unassigned USB Vendor ID (VID) and Product ID (PID) combination. In my app, I use VIDs to identify FIDO devices, and the unassigned VID/PID is causing issues with proper device identification. Would it be possible to consider using a properly assigned VID/PID? For open-source projects, there are a few options: - **pid.codes** - Free PIDs for open-source projects - **OpenMoko** - Allocates PIDs under their VID for open-source projects - **Raspberry Pi** - Has a PID allocation program for projects using RP2040/RP2350: https://github.com/raspberrypi/usb-pid Thanks again for this project! Best regards, Michel

polhenarejos commented

2026-01-08 17:53:20 +08:00

(Migrated from github.com)

This is something we thought but we finally discarded it due to:

We do not ship or produce hardware.
Some apps may require specific VID/PID, so we leave the decision on which VID/PID to use to the user.
Most of the cases will finally use other VID/PID than ours.

So, in the end, having our own VID/PID would be used only for the initial acquisition. Could you provide more information about your use case?

This is something we thought but we finally discarded it due to: - We do not ship or produce hardware. - Some apps may require specific VID/PID, so we leave the decision on which VID/PID to use to the user. - Most of the cases will finally use other VID/PID than ours. So, in the end, having our own VID/PID would be used only for the initial acquisition. Could you provide more information about your use case?

mimi89999 commented

2026-01-08 18:26:05 +08:00

(Migrated from github.com)

I tested with the release images from this repo and noticed that an unassigned VID is used. Since there's no specific VID to match, I had to detect by product name instead: 99fd0ec12b

It would be good if the provided release images had a proper VID/PID, even though users can change it.

I tested with the release images from this repo and noticed that an unassigned VID is used. Since there's no specific VID to match, I had to detect by product name instead: https://github.com/mimi89999/Authnkey/commit/99fd0ec12b671d967e1f6aee12a6e93d8bb1911c It would be good if the provided release images had a proper VID/PID, even though users can change it.

polhenarejos commented

2026-01-26 01:47:40 +08:00

(Migrated from github.com)

Finally, we got an official VIDPID allocation instead of dummy FEFF:FCFD.

Pico HSM: 2E8A:10FD
Pico Fido: 2E8A:10FE
Pico OpenPGP: 2E8A:10FF

Finally, we got an official VIDPID allocation instead of dummy FEFF:FCFD. - Pico HSM: `2E8A:10FD` - Pico Fido: `2E8A:10FE` - Pico OpenPGP: `2E8A:10FF`

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dearsky/pico-fido#242