search

solokeys / solo1

Solo 1 firmware in C
https://solokeys.com/
Other
2.31k stars 273 forks source link

Windows 10 FIDO2 NFC Compatibility #466

Open MichaelGrafnetter opened 4 years ago

MichaelGrafnetter commented 4 years ago

Hi, I have been playing with my new Solo Tap USB-A with firmware version 4.0 and I can't make it work on Windows 10 when it is connected through a NFC reader from Feitian. It always ends with an infinite loop of "New hardware found" and "Device disconnected" messages. FIDO2 keys from Feitian work seamlessly with this reader. Is there please an easy fix for this?

image

aseigler commented 4 years ago

Is there a label on the back of the reader with any part numbers? There were a series of NFC fixes that went in August 2019 (#280, #297) that sound very similar to the experience you describe, but if you are using 4.0 it has all of those patches already.

MichaelGrafnetter commented 4 years ago

Hi @aseigler , thanks for your reply. No part numbers are listed, only these specs on manufacturer's website.

aseigler commented 4 years ago

About the only "easy fix" you might try is having the Solo powered via USB while simultaneously using it on the NFC reader. This will rule out a low power condition. If that doesn't help (and I doubt it will), it's probably debugging time, comparing the request/response between the Feitian and Solo tokens with the WebAuthN operational event log or with USBPcap in Wireshark.

MichaelGrafnetter commented 4 years ago

USB power did not help. 😒

kyleharte commented 3 years ago

I'm assuming it's an issue with the way Windows handles FIDO keys. I'm assuming it could be the NFC timeout maybe

MichaelGrafnetter commented 3 years ago

I just performed more NFC tests on Windows 10:

It would seem that Solo Key is only incompatible with that particular reader model.