Generally this is a ROM mask option that is loaded for emulation. It has to be set at the time of manufacturer basically. Fidesmo P40 chips had my fair classic emulation turned on but there are issues with the emulation. For example, you cannot specify UID. That in itself is kind of annoying. I believe the p60 version had desfire emulation enabled, but I don’t believe the P71 version has any emulation option loaded. This was because the option burned up a lot of memory in the ROM mask and not a lot of customers or people were using it.
My thought being, Amal and the Developers can use this Poll as a gauge to see what the customers want, and MAY focus their time on the frontrunners
But before I do that, Here’s an update on the progress,
ALMOST ALL HAVE BEEN DEVELOPED
Vivokey OTP
VivoKey U2F
VivoKey WebAuthn
VivoKey PGP
VivoKey NDEF
VivoKey NAK
BitCoin Wallet ( Not in the original list )
Vivokey GIDS * isn’t worth deploying at this time since Microsoft is abandoning it over Fido / azure…
Therefore The only remaining Applets on the original list are
VivoKey KeePass (would need specific development outside of an applet and gids )
VivoKey PIV
I would still like to see a KeePass at somestage, but it will probably be a lot of work and expensive to develop, so who knows if /when we will see that…
Does anybody have more suggestions of what you would like to see developed and added to the Vivokey APEX arsenal?
Just reply to my post, I will give it a couple of weeks and build another poll so the developers can keep an eye on it for ideas / inspiration…
We are basically at the stage now where our fido2 applet is “certification ready”. The version currently available on Fidesmo is feature complete, thoroughly tested, and it is what we will be taking through the certification process. It’s what I am running on my Apexes now.
Of course, certification could reveal other issues but I really doubt it. The only difference that’s guaranteed is that the attestation certificate loaded in with the certified version will be different and will appear differently in the Fido metabase. For most people though, that won’t matter.
I’m not sure keepassxc FIDO2 is “in development” per se. I’m working on an implementation for keepassxc, pykeepass, and keepassdx (android), but it’s a spare-time thing.
I contributed a spec and have it half-working in Python code but it’s a ways out if nobody else implements it.
Just like everything else, the answer is… It depends. Windows Hello is a platform for authentication, but using a Fido token with Windows for login is only possible in your computer is a member of an Entra ID (formerly azure ad) domain.
As far as I know, you don’t necessarily need a certified token to use it with entra ID but you can’t use it by default. You would have to go through a process of setting up your domain to accept unknown and/or un-certified tokens. The default is a short list of certified tokens… such that you actually have to apply to have your certified token accepted without question. So the first hurdle is getting certification and the next hurdle is applying to Microsoft to have your token recognized by their system as something to accept as secure by default.
