Closed scateu closed 6 years ago
Have you confirmed that your token works for other sites, like Google? I wonder if the button on yours might be broke.
It works for google, dropbox, fastmail, even for pam.d(linux/macOS), and firefox u2f plugin.
So it can be sure there is some compatibility issue with FIDObooster.
I have written to them, and get a response that they are working on it.
@scateu maybe you are hitting https://github.com/conorpp/u2f-zero/issues/36 ? can you check if the key is full already ?
Actually, I tried after 'python client.py wipe' (and 5 press)...
python client.py wipe
@scateu to wipe you need to press button 5 consecutive times. The client tool will let you know if it worked.
"Actually, I tried after 'python client.py wipe' (and 5 press)..."
and it did wipe.
$ python client.py wipe
opened None
Press U2F button repeatedly until the LED is no longer red.
Wipe succeeded
I just checked the debugging output and registration seems fine. It's likely an issue with FIDO Booster not handling something right. For instance, when all 15 slots are use up, the u2f zero replies with a valid error response indicating there is no memory. Yet FIDO booster continues to send repeated registration requests.
The program probably has the typical try/except while loop. It probably runs into an error parsing the u2f zero registration certificate which is different from Yubico's cert, causing it to resend another registration. Yubico is probably what the FIDO Boost authors tested against.
Thanks. I have reported this issue to Vancosys. Hope this information will help them debug FIDO booster.
(CC: Bahram and Geoff from vancosys.com)
-- Wang Kang Blog: http://scateu.me Fingerprint: 011F 0492 97D6 5D75 8AC4 6458 D43F 3CE2 3353 B7BD HAM Callsign: BH1RLW
On Mon, 5 Dec 2016, Conor Patrick wrote:
I just checked the debugging output and registration seems fine. It's likely an issue with FIDO Booster not handling something right. For instance, when all 15 slots are use up, the u2f zero replies with a valid error response indicating there is no memory. Yet FIDO booster continues to send repeated registration requests.
The program probably has the typical try/except while loop. It probably runs into an error parsing the u2f zero registration certificate which is different from Yubico's cert, causing it to resend another registration. Yubico is probably what the FIDO Boost authors tested against.
-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/conorpp/u2f-zero/issues/40#issuecomment-265070322
Is this still being looked at or can I close?
I am trying to program the latest firmware into U2F Zero. After that, I'll test it again.
Assuming I can close this, let me know if there are still issues.
On Windows 10, I also didn't succeed using U2F-zero with FIDOboosterUno. I bought my U2F-zero here around Xmas. Tested in february. So maybe issue should be re-open...
There was a faulty batch shipped around Christmas that was fixed by early January. Email me your order ID and we can go from there
http://www.vancosys.com/fidobooster/
When I try to register it through "FIDOboosterUno for Windows 10 64bit",U2F-Zero does give an indication for me to press the button. But FIDOboosterUno doesn't continue after I pressed it. (The U2F-Zero device still keep the indication lights on)
While it works well for my Yubikey Neo.
Plus, what can I do if I want to debug this issue?
Thanks.
FIDOboosterUno Download links
Windows 10
Windows 7/8