1480425 - Yubikey (U2F) not recognized when hotplugged

Status: UNCONFIRMED

(Core :: DOM: Device Interfaces, defect, P3)

Description

[mawizard-thomas]

This is a follow-up to bug #1460301. Even with that bugfix my yubikey neo still never works when hotplugged on any of my windows machines. It works fine when inserted before U2F is requested. The demo application from u2f-hid-rs doesn't work when hotplugged either. 

Where the U2F ping command was disturbed/corrupted by interleaved CCID packets before, now the version check command fails. 
The U2FHID_INIT command succeeds and has the correct response. The u2f-hid-rs library then sends a U2FHID_MSG wrapped APDU message with instruction U2F_VERSION (3). Right after this message is sent on the USB bus, CCID messages are exchanged by the windows smartcard driver and I think this confuses the yubikey. It does respond after a while using the right channel ID and U2FHID_MSG command, but responds with the 2-byte APDU response 6E 00. As far as I can tell this is an APDU error status 'class not supported'.

When the device is plugged in already and the CCID messages are not present during the initialization it works fine.