As I understand it, instead of the website or online service storing your password (in a, supposedly secured way), with passkey your password manager stores a private key and the online service stores a public key (or rather a lock). The key and the lock are paired together cryptographically (mathematical functions that are non-reversible). Now when you login with passkey, the service sends a challenge generated from the lock, that can be solved only with the matching private key, your password manager solves the challenge and your authenticated. Locks and keys were not exchanged during the process, and services never store your key. Everything happens automagically.

It actually uses the same protocol used is some hardware security keys such as Yubikey and Solokeys. The problem remains the same as with hardware security keys, adoption and support, compatibility. It's very rare that a service supports these options, although they exist for a while.

Anyone feels free to correct me if I wrote something wrong. I am by no mean an expert.

[–] cron@feddit.org 16 points 3 months ago (1 children)

Your explanation is correct.

For me, the critical issue is still compatibility. Not all password managers support passkeys, not many sites support passkeys etc.

[–] synapse1278@lemmy.world 2 points 3 months ago

Yes, I have my Solokey for a while. I can count the compatible services I use on the fingers of one hand. Passkey, as of today, even fewer...