Use picoforge configure error

[ncmro7]

Before filing

• I searched the existing issues and this is not a duplicate.
• This is not an exploitable security bug (those go to a private advisory, not here).
• I can still reproduce it on current main.

Area

Not sure

Firmware build

RS-Key 0.3.X

Board

waveshare rp2350 zero

Host environment

Windows 25H2，picoforge 0.6.0

What happened

librekeys/picoforge#102
Just like in this issue and my reply, there are still problems when trying to change RS-Key parameters using picoforge: you can't modify VIDPID and the name at the same time. Sometimes if you change the VIDPID, the name resets to default; if you change the name, the VIDPID resets to default. Also, LED-related settings don't seem to work either.

Also, when using picoforge to modify pico-fido2, if the VIDPID isn't Yubikey's VIDPID but the name is Yubico Yubikey, Yubico Authenticator works fine. But for RS-Keys where the name is changed to Yubico Yubikey via picoforge, Yubico Authenticator doesn't work. (Same with compilation)
update Yubico Authenticator log below

I'm not sure how much this is related to the firmware, but I checked the PR and saw some adaptations for picoforge, so I decided to open an issue here.

Steps to reproduce

flash device
use picoforge configure device

Output / logs

22:06:08.775 [helper] ERROR: Traceback (most recent call last):
22:06:08.775 [helper] ERROR:   File "authenticator-helper.py", line 40, in <module>
22:06:08.775 [helper] ERROR:   File "helper\__init__.py", line 149, in run_rpc_pipes
22:06:08.775 [helper] ERROR:   File "helper\__init__.py", line 127, in run_rpc
22:06:08.775 [helper] ERROR:   File "helper\device.py", line 103, in __init__
22:06:08.775 [helper] ERROR:   File "helper\device.py", line 155, in __init__
22:06:08.775 [helper] ERROR:   File "helper\device.py", line 159, in scan
22:06:08.775 [helper] ERROR:   File "helper\device.py", line 165, in list_children
22:06:08.775 [helper] ERROR:   File "ykman\pcsc\__init__.py", line 278, in list_devices
22:06:08.775 [helper] ERROR:   File "ykman\pcsc\__init__.py", line 114, in __init__
22:06:08.775 [helper] ERROR:   File "ykman\pcsc\__init__.py", line 69, in _pid_from_name
22:06:08.775 [helper] ERROR:   File "yubikit\core\__init__.py", line 156, in of
22:06:08.775 [helper] ERROR:   File "enum.py", line 793, in __getitem__
22:06:08.775 [helper] ERROR: KeyError: 'YK4_'
22:06:08.775 [helper] ERROR: [PYI-23088:ERROR] Failed to execute script 'authenticator-helper' due to unhandled exception!
22:06:39.823 [desktop.init] INFO: Copying log to clipboard (7.3.1)...

Anything else

No response

[netll]

I've also noticed this issue. My current approach is to specify these four essential build parameters to fit my board: VIDPID, FLASH_SIZE, LED_KIND and LED_PIN. With these configured at build time, once the firmware is compiled and flashed successfully, no extra software or configuration tools are required — the board works right out of the box.

it's great that you raised this issue. It will help draw more attention to this matter.

[ncmro7]

I've also noticed this issue. My current approach is to specify these four essential build parameters to fit my board: VIDPID, FLASH_SIZE, LED_KIND and LED_PIN. With these configured at build time, once the firmware is compiled and flashed successfully, no extra software or configuration tools are required — the board works right out of the box.

it's great that you raised this issue. It will help draw more attention to this matter.

That means every time there's an update, you have to compile the firmware yourself, which might be a bit inconvenient for people who only use it on Windows (I just tested the firmware released on GitHub, and it will overwrite the names and LEDs from my own compiled configuration, the VID/PID is still unclear， i forget build it😂)

[ncmro7]

I've also noticed this issue. My current approach is to specify these four essential build parameters to fit my board: VIDPID, FLASH_SIZE, LED_KIND and LED_PIN. With these configured at build time, once the firmware is compiled and flashed successfully, no extra software or configuration tools are required — the board works right out of the box.
it's great that you raised this issue. It will help draw more attention to this matter.

That means every time there's an update, you have to compile the firmware yourself, which might be a bit inconvenient for people who only use it on Windows (I just tested the firmware released on GitHub, and it will overwrite the names and LEDs from my own compiled configuration, the VID/PID is still unclear， i forget build it😂)

Maybe I can make another suggestion. Picofido2 wouldn't do this. I wonder if the author will see this reply and change it.

[TheMaxMur]

@ncmro7

Last week, we discussed testing PicoForge with RS-Key. I've put it on hold for now, wanting to polish the firmware for a better user experience. Overall, I'm almost done; I'll be picking up PicoForge again soon and will keep you updated on the progress.

For now, Windows users can compile the firmware via nixos wsl, which I think is a perfectly viable option.

[ncmro7]

@ncmro7

上周，我们讨论了用RS-Key测试PicoForge。我暂时搁置了，想先完善固件以提升用户体验。总体来说，我快完成了;我很快会重新入手PicoForge，并会持续向大家更新进展。

目前，Windows用户可以通过nixos wsl编译固件，我认为这是一个完全可行的选择。

The current firmware is really perfect.💕

[netll]

I've also noticed this issue. My current approach is to specify these four essential build parameters to fit my board: VIDPID, FLASH_SIZE, LED_KIND and LED_PIN. With these configured at build time, once the firmware is compiled and flashed successfully, no extra software or configuration tools are required — the board works right out of the box.
it's great that you raised this issue. It will help draw more attention to this matter.

That means every time there's an update, you have to compile the firmware yourself, which might be a bit inconvenient for people who only use it on Windows (I just tested the firmware released on GitHub, and it will overwrite the names and LEDs from my own compiled configuration, the VID/PID is still unclear， i forget build it😂)

Yep, I build the firmware myself for every update. It’s really not much hassle — once you have the build environment set up, rebuilding for each update is very fast.
The firmware the author releases on GitHub only provides basic working functionality and isn’t pre-configured for YubiKey emulation. I suspect this is likely to avoid copyright issues or unnecessary legal disputes.

[TheMaxMur]

In any case, I think the build here is much simpler than in pico-fido. At least there's documentation for it xd

[TheMaxMur]

@ncmro7 check now on master branch of PicoForge

[ncmro7]

@TheMaxMur It's too late, I'll test it the next day (could you add https://makerworld.com/zh/models/2655625-pico-2-zero-fido2-case-rp2350?from=search#profileId-2936496 to https://themaxmur.github.io/RS-Key/hardware.html? That's what I consider a perfect Waveshare RP2350 Zero case).

[ncmro7]

@TheMaxMur
It's worth noting that the generic release firmware with modified vidpid and product name can be used in ykman and the yubico authenticator for Android, but not on Windows.
The Windows logs are the same as those given at the beginning of the issue.
That's weird