Closed landaire closed 8 years ago
Looks like we can't write to that key because:
The Special Edition Octocat Key is a FIDO U2F Security Key, created for GitHub users. It is a U2F-only security key, meaning you cannot configure the key for any other use. Because you cannot configure this special key, this key is not recognized by the YubiKey Personalization tool.
I wonder how this key differs from the regular ones. Is it a software or hardware limitation ?
Hmmm, I didn't see that. I also didn't try writing to the key since I figured that the change to yubikey-core would work its way into the GUI tool where I could actually view information about the device.
I really just wanted to see serial/firmware/etc. in the think that it would still support the device but be smart enough to put it into an immutable state (I mean, the features supported are right there on the side panel...). Anyways, I tried to query at least the serial number from the CLI tool and kept getting a serial of 0 for slots 0x0-0xFF and flag 0 so some hardware features may not be supported. It's kind of fun hacking on this thing though.
So the reason the product 0x120 is not included in the list of devices in this library is that it is a u2f only key which this project doesn't know at all how to speak with. This project only speaks with the OTP interface of a YubiKey so sending the OTP feature reports to the U2F interface will result in confusion.
Per the title, this adds support for the U2F sent out as part of the GitHub promotion and fixes #65.