> Your device supports passkeys, a password replacement that validates your identity using touch, facial recognition, a password, or a PIN.
> Your device supports passkeys, a password replacement that validates your identity using [...] a password
What is being accomplished here if I choose to activate a "passkey" using a "password" for GitHub?
The implementation of the credentials manager on the device storing the passkey should also ensure 2factor auth for use of the key.
Further passkeys are highly phishing resistant since they are bound to one specific domain and the passkey manager enforces that it is only transmitted to said domain.
It is basically a phishing , credentials stuffing, brute force resistant password that should ensure 2factor authentication.
It is pretty much the spot between dedicated hardware keys and still usable for the normal guy.
The only thing I dislike is that every provider can lock you in their "passkey ecosystem" since they only sync between them etc.
Another things is I "lost access" to passkeys.io while trying out passkeys. My phones Bluetooth was switched off, and by the time my phone created and saved a passkey, it timed out on the computer. So now I can't login with that passkey and it only fails. Seems like I'm locked out now...
> Another things is I "lost access" to passkeys.io while trying out passkeys. My phones Bluetooth was switched off, and by the time my phone created and saved a passkey, it timed out on the computer. So now I can't login with that passkey and it only fails. Seems like I'm locked out now...
What does "backing up" the key achieve over and above just registering another key?
I had added that key as a plain fido security key and it didn't let me add it as a passkey. So, I removed that key from the list of security keys and added it as a passkey.
