About HW FIDO2 Provider

Should I rename it? If you think so, any suggestion?

The app supports the secure element of the phone in addition to hardware keys.

#android #passkey #passkeys #hwFido2Provider

Yes, change!
50%
No, that's fine
50%
Poll ended at .
hw-fido2-provider

hw-fido2-provider

Codeberg.org

Registrations of non-discoverable passkeys are now supported by #Vanadium:

https://github.com/GrapheneOS/Vanadium/pull/927/files#diff-0e95e0a3b78b085b4f15b22ab7ca651e3f0aae187f4ce408ac53c83f6148da2d

The non-discoverable keys are often used without PIN as a 2FA, like on Codeberg, Gitea, etc. Or they are used with a PIN but after requesting the username, like on Nextcloud.

Using non-discoverable key with a PIN after requesting the username has the advantage to not use one of the slots of the key manager - which are often limited on hardware tokens - but may allow someone to verify if a username is known by the application (most of the time, this is possible with other features too). So it can be a great compromise, especially if the user is able to choose what kind of key they want to use.

It's now possible to register them on any credential manager (like #KeePassDX or #HWFido2Provider)

For the record, Firefox has fixed it recently too

#Passkeys #Fido2 #Android #GrapheneOS

142.0.7444.48 by vanadium-staging · Pull Request #927 · GrapheneOS/Vanadium

Update/port patches for 142.0.7444.48.0 Update to 142.0.7444.48 increment config app version to 131

GitHub