ve7jtb
commented
3 months ago This issue with the lightning transport will block the certification of the only lightning key.
Closed ve7jtb closed 2 months ago
ve7jtb
commented
3 months ago This issue with the lightning transport will block the certification of the only lightning key.
iirachek
commented
3 months ago The v1.7.20 build with a fix for this is available for download.
By submitting this issue you are acknowledging that any information regarding this issue will be publicly available.
If you have privacy concerns, please email conformance-tools@fidoalliance.org
FIRST PRE CHECK
What protocol are you implementing?
NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.
What is your implementation class?
If you are platform authenticator vendor, please email conformance-tools@fidoalliance.org
What is the version of the tool are you using?
v1.7.19-1
What is the OS and the version are you running?
For desktop tools
For UAF mobile tools
Issue description
[Authr-Generic-1 Generic FIDO protocol tests] Previous versions of the test tool ignored unknown transports in getInfo. Now it seems to have a static list.
AssertionError: getInfo.transports contains value lightning NOT in defined in: [usb,nfc,ble,internal]: expected [ 'usb', 'nfc', 'ble', 'internal' ] to include 'lightning' at n.eval (eval at compileCode (js/sandbox.js:25:26),:5627:24)
We did have lightning as a transport for a while. Apple objected to differentiating between USB and lightning so it was eventually taken out of WebAuthn L2. However the one security key that supports lightning advertises it in getInfo as some applications do look for it. The hybrid transport will also be a problem for some authenticators. I think it is wrong to error on unknown transports, but at least lightning and hybrid need to be added.