Invalid CBOR in GetInfo response

[agl]

Just poking at this device with Chrome, after flashing firmware 2.1.0:

Chrome rejects the GetInfo response because the CBOR is invalid and thus treats this firmware revision as U2F-only. Specifically, the entries in the CBOR map are incorrectly ordered. See section 6 on ordering.

[conorpp]

Thanks for reporting. I just pushed a fix for this and tested Chrome is able to register+auth with FIDO2 without falling back to U2F.

Do you have a hacker/reprogrammable Solo and would be able to test on your side? If so, you can update with my fix.

solo.hex.zip

pip3 install python-solo
unzip solo.hex.zip
solo program bootloader solo.hex

[0x0ece]

Good catch! Just tested this new firmware on Safari 12.1, the future is passwordless :)

[agl]

Do you have a hacker/reprogrammable Solo and would be able to test on your side? If so, you can update with my fix.

I have one on order.