On 2025-12-29, whistlez <[email protected]> wrote: > Dec 29 14:21:29 /bsd: uhidev5: iclass 3/0 > Dec 29 14:21:29 /bsd: uhid3 at uhidev5: input=64, output=64, feature=0 > > and below is what Chromium responds if I try to use it: > > [2398:4653927621336:1229/144223.510710:ERROR:components/device_event_log/device_event_log_impl.cc:198] > [14:42:23.498] HID: hid_service_fido.cc:87 no response /dev/fido/0 > > and this is the log from usbdevs > > Bus 000 Device 006: ID 1d50:60fc OpenMoko, Inc. > > According to ChatGPT, OnlyKey doesn't have a standard FIDO > implementation but a custom/proprietary one, which appears to be the > source of the problems. > Permissions seem correct... I'm not sure what else to say. I've tried > using yk manager to detect it, but obviously, since it's not a YubiKey, > it doesn't see it. > > What do you recommend I do?
Two fairly simple options: patch the kernel to allow using yubimey, or use yubikey on another OS. (You could even just have it write the otp into a text editor and re-type it on the OpenBSD machine if you want). > If it's not compatible, please remove that comment on undeadly.org > (placed by an unknown person) that misleads people. undeadly is a third party site, but even if it wasn't, probably easiest just reply to the comment and say that it doesn't work. -- Please keep replies on the mailing list.
