I have P71s which show up as Yubikey 3 and one shows up as Yubikey 4, what defines the shown version?
Which .cap makes them the newest Yubikey?
Hello, which applet are you interfacing? TOTP? HMAC-SHA1? Which app are you using to read the applet, on what device?
I mean… to answer the question directly it’s up to the yubico app. It pokes and prods to try to figure it out. Exactly what it’s doing isn’t perfectly known but @StarGate01 has some ideas. Basically we believe it looks for certain types of services on the device and after evaluating exactly what’s offered on the device, it makes a determination as to what product it thinks it is.
There isn’t a “yubikey” cap file… various services are broken out and provided as individual insoluble applets. Because of this, there is no solution where you’ll be able to load a single cap file and have “the latest yubikey”.
In addition to this, I believe some of the more recent products actually implement a way to determine what product it is by querying it. I don’t think there are any plans to implement a straight up “emulate a Yubikey” type applet.
2 Likes
We do not support the proprietary Yubikey management functionality, only (some) of the offered standardized crypto protocols like TOTP, FIDO and HMAC-SHA1. Older Yubikeys worked the same way, I.e. did not have this management applet, which is why some yubikey tooling defaults to assuming the Apex is on of those old Yubikeys.
2 Likes