serial number detection on hardware keys

[bioscopic]

Noticed on some hardware keys the serial number does not necessarily detect an accurate serial number for onlykey. solokey and yubikey seem to detect the correct serial number when the user executes the keyroostctl list under FIDO HID devices.

[framefilter]

Looked into this a bit — thank you. keyroost already talks to the OnlyKey on its FIDO interface (1d50:60fc, CTAP usage f1d0:0001), so keyroostctl fido info reaches it over CTAP2 (recent firmware; older OnlyKeys were U2F-only). The serial=1000000000 isn't a misread — we print the USB iSerialNumber verbatim, and OnlyKey's firmware hardcodes that value (the unique-serial code is commented out upstream), so every unit reports it. Accurate, but not unique. v0.7.0 will add OnlyKey-aware handling: label it "OnlyKey" and treat that serial as a non-unique placeholder, falling back to the device path. One limit: the OnlyKey exposes no CCID interface, so our OATH/OpenPGP/PIV (PC/SC) commands can't reach it — only the fido group applies. Keeping open for the v0.7.0 work. I'll try to get test hardware in hand soon to integrate Onlykey hardware as tightly as possible, though v0.7.0 might ship based on their published spec without comprehensive hardware testing. Thanks @bioscopic

[framefilter]

Quick honest status for v0.7.0: the OnlyKey now gets a proper name via its FIDO2 AAGUID, but the serial handling I described — recognizing the hardcoded 1000000000 as a non-unique placeholder and falling back to the device path — didn't make this release. I'd rather verify that against real OnlyKey hardware than ship it blind, so I'm keeping this open and tied to getting a unit in hand. Thanks for the clear report, and for your patience @bioscopic.