libfido2 won't recognize Kensington VeriMark Guard USB-C Fingerprint Key

[arash-acceptto]

What version of libfido2 are you using? Tested on v1.8 and v1.7

What operating system are you running? Tested on Windows 10 and macOS Big Sur

What application are you using in conjunction with libfido2? Tried using fido2-token -L to check for device detection.

How does the problem manifest itself? Basically anything that calls into the fido_dev_info_manifest(...) won't recognize the key. We're using a Kensington VeriMark Guard USB-C Fingerprint Key

Is the problem reproducible? Yes.

What are the steps that lead to the problem? Run fido2-token -L

Does the problem happen with different authenticators? No, we've been using libfido2 with YubiKeys and Feitan authenticators with not issues.

This issue only happens with the Kensington VeriMark Guard USB-C Fingerprint Key

Please include the output of fido2-token -L.

fido2-token -L

$ fido2-token -L

It's always empty with the Kensington VeriMark authenticator.

Please include the output of fido2-token -I.

fido2-token -I

$ fido2-token -I <device>

fido2-token -L is always empty with the Kensington VeriMark authenticator, so there's no device to use with the -I here.

Please include the output of FIDO_DEBUG=1.

FIDO_DEBUG=1

$ export FIDO_DEBUG=1
$ <command1>
$ <command2>
(...)
$ <commandn>

Same results as before, no additional information is available in the output.

---

We didn't step into the functions in the *hid_*.c to determine why/where it fails, please let me know if I can provide more information.

Thanks,

[martelletto]

Hi, thank you for the report. There's unfortunately not much to go on. On macOS, does the device show up in ioreg -p IOUSB and hidutil list? Is it usable from Chrome?

[arash-acceptto]

Hi Pedro, thank you for your response.

Yes, it does work in Chrome, both macOS and Windows.

hidutil list

0x47d    0x8055    0x1100000  61904     1     0x100005c21 USB       AppleUserHIDDevice         VeriMark Guard Fingerprint Key     AppleUserUSBHostHIDDevice (null) 

ioreg -p IOUSB | grep Veri

 | +-o VeriMark Guard Fingerprint Key@01100000  <class IOUSBHostDevice, id 0x100005c19, registered, matched, active, busy 0 (36 ms), retain 28>

Please let me know if we can provide more information or send you a VeriMark authenticator device for further investigation.

Thanks,

[martelletto]

Hi Aarash, thank you for the feedback. I believe testing with the authenticator itself would be the quickest way of fixing the problem. Could you ping me at pedro@yubico.com?

[arash-acceptto]

Hi Pedro, Sure, I'll get in touch shortly. Thank you.

[martelletto]

Fixed in e093ccf04. Thank you for the report and support!