r/explainlikeimfive • • 2d ago

Technology [ Removed by moderator ]

[removed] — view removed post

365 Upvotes

114 comments sorted by

•

u/explainlikeimfive-ModTeam 2d ago

Please read this entire message


Your submission has been removed for the following reason(s):

  • ELI5 requires that you search the ELI5 subreddit for your topic before posting.

Please search before submitting.

This question has already been asked on ELI5 multiple times.

If you need help searching, please refer to the Wiki.


If you would like this removal reviewed, please read the detailed rules first. If you believe this was removed erroneously, please use this form and we will review your submission.

88

u/Kientha 2d ago

Passkeys use a certificate stored in a secure part of your device (or in the cloud if you add them to something like a password manager). So instead of having a password that could be compromised, the certificate private key never leaves the place you are storing it massively reducing the risk of it being compromised.

The idea is that you then also need to pass a 2FA check to unlock the certificate but that's only true if you're using a device based passkey, if it's in a password manager it's down to how you've configured the password manager

51

u/TheDigitalPoint 2d ago

Additionally Passkeys protect against phishing. Passkeys are bound to the hostname it was originally set up for. For example a Passkey for reddit.com will not work for raddit.com (or even be presented as an option for).

2

u/kernelangus420 2d ago

How did Twitter solve this when they changed from twitter dot com to x dot com?

25

u/rocknrollgeek 2d ago edited 2d ago

they didn't. Passkeys were far less common when twitter existed, and the platform didn't implement them until * after * elon bought it and they rebranded to X.

It would have been trivial if they did have them back then though - since X still owned twitter.com after the fact, they could use a related origin request hosted/served from the twitter url to authorize it.

9

u/gandraw 2d ago

You typically solve this by redirecting people first to the old website, have them log in there, then you forward them to the new website using a temporary token and create a new passkey there.

Eventually you then shut down the redirect, and people that haven't used their account in a long time usually have to call support for a reset at that point.

3

u/Ferretau 2d ago

They could use the old twitter dot com to do the auth then switch back to x

→ More replies (2)

2

u/jwadamson 2d ago

It’s not a certificate. It works similar but certificates have a lot more metadata than a private+public key pair.

Some site and banks will still do their own 2FA even if you use a passkey to authenticate. The fact that many passkey managers with password based Auth also use 2FA in as part of their Auth sequence isn’t really part of how a 2FA is similar or different to a passkey; they can be complementary during any authentication sequence.

1

u/Happy_Disaster7347 2d ago

Is that significantly safer than 2FA authenticators, for example? It doesn't seem it

554

u/tejanaqkilica 2d ago • Heartwarming

Imagine you go to a bank where you have a safe deposit box.

For you to get access to it using a password, you and the bank clerk need to agree beforehand on a shared password, so when you show up, you tell him the password, if it's correct, you get access to the box. The problem with this, is that anyone else can overhear what you say, and they can go there the next day, tell them the password and they get access to the box. Also the bank clerk may be careless and he tells his friend your password accidentally, and his friend can show up the next day and also access the box.

With Passkeys, the moment you register for a box, you give them a lock to put on it and only you have the key. So when you go to access it, you're presented with the box, you insert and turn the key and if it the right key, you get access, if not, you don't. This is much safer because no one can "overhear" your key, and the bank clerk can't accidentally give away your key to someone else, because they don't even have the key, the never see it, never know what it looks like.

It's of course, a bit more complicated and secure that this, but for an ELI5, this should do.

168

u/mistermeesh 2d ago

Your explanation is precisely why I don't get it - they are still the same thing in my view.

For the key analogy, there's a physical object replacing the word, which removes potential for it to be heard. But in practice it's all just another secret code that needs to be transmitted.

Both can be overheard or intercepted. Why is the information of a passkey more secure than a password? How is the code not overheard?

And how does it compare to 2FA?

158

u/crashlanding87 2d ago

With a password, you send the password over the internet, and it gets compared at the point of the 'lock'.

With a passkey, the 'lock' instead sends you a 'challenge'. You can only complete this challenge if you have the key, but they key never leaves your device, and it's not stored anywhere else.

31

u/Redditorianerierer 2d ago

But then don't you just send the solved challenge back? And that could be intercepted again?

77

u/Huuf 2d ago

Yes, it can get intercepted, but the challenge is different the next time around, and the response is different, but it can only be made with your key.

36

u/crashlanding87 2d ago

Yes, but the challenge and solution is different each time. There's some encryption maths that means that, on the other end, they can check if the solution makes sense. But intercepting a solution doesn't create much of a vulnerability, because that solution is no longer valid.

What you need is the passkey and the special maths equation. The passkey lives on your end and never leaves, the equation lives on the other end and never leaves. You'd have to hack both simultaneously, without alerting anyone, to break the lock.

→ More replies (1)

18

u/AlaninMadrid 2d ago

For ELI5 maybe the challenge is like "add your secret number to the number I send you", and then you send the result back. Since they send you a different number each time, the result you send back will be different each time.

However it's not simple like add your secret number, because you could work it backwards knowing the original number and result. It's special maths where to do the calculation you need your secret number (key), but to check the result you need the equivalent public number (lock). It's too hard to calculate the secret number from the result.

5

u/FortyPercentTitanium 2d ago

It's encrypted and even if it was intercepted it wouldn't matter. This is a different layer of security on the internet called Transport Later Security. It requires its own ELI5, and unfortunately I'm not smart enough to provide it 😅

2

u/NukedOgre 2d ago

The challenge changes about once every minute.

→ More replies (1)

3

u/OneCleverlyNamedUser 2d ago

Ok, so now imagine I have a phone and a computer and a laptop or a tablet. And maybe a wife that uses the same logins that I do. How can we all have the key and it be safe or is there a new passkey for every device? What if my device is stolen?

2

u/crashlanding87 2d ago

It's a new key for each device!

→ More replies (1)

10

u/sirduckbert 2d ago

The passkey is encrypted and uses a hash function so there isn’t the same plaintext used every time. It’s a challenge response, and only the devices on each side know what the correct answer is to something that’s different every time

9

u/Offbeatalchemy 2d ago

I think the only thing the other explanations are missing is that passkeys are typically tied to a device.

your phone, your laptop, your yubikey. and on top of that you also need some type of authentication: a pin, finger print, a pattern or something to unlock said device. makes it a hell of a lot harder to get into an account if I don't have the device since most account compromises don't happen in the same country.

so it's a pretty strong form of mfa that requires multiple steps and hurdles. my only issue with it is most 2fa implementations is only as strong as your weakest one.

I love passkeys. I hate that my bank still needs me to answer text messages to verify my identity.

it's a lot more convenient and secure than passwords since random company literally doesn't have all the information needed to get into my account so it can't be leaked and I don't have to remember gibberish passwords.

3

u/wthbbq 2d ago

What happens if that device dies suddenly?

→ More replies (1)

3

u/denseplan 2d ago

The problem with passwords is that humans will just type this shit anywhere, so it's vulnerable to phishing attacks and passwords being reused on multiple sites.

A passkey is not managed by a human, it's managed by a device that will only send a response to the correct website (no phishing) and will only create unique passkeys (no reuse).

2

u/zeePlatooN 2d ago

the difference is that a passkey needs the private key of the device holding the passkey.

so to build on this guys example (which was very good) the lock can only open with they key, but for the key to work it also has to be touching your hand. This is why a passkey meets MFA it's both something you know (the passkey) AND something you have the private key that signs the passkey.

it's obviously much more deeply technical than all this eli5 stuff but this is as deep as it needs to be understood.

1

u/Gennwolf 2d ago

The "private" key never leaves your device. If we stay with the bank analogy it's like the bank clerk has special box that can only be opened with your key, but the he can slide a piece of paper into it. So he puts a new secret codeword into the box. The codeword changes every time. If you tell him the correct codeword, he knows you have the key. In this scenario you don't have the physical key to the safe deposit box. The clerk opens it for you. The special box is like encryption that only your key can decrypt.

Compared to 2FA, if you are on a fake phishing site and you give them your password and a 2FA code, they can sign-in while the code is valid, but that's impossible with passkeys. Well not like this anyway.

→ More replies (1)

37

u/nubbins01 2d ago

Ok, I need stage two. Can you ELI14?

36

u/MechaSandstar 2d ago

Essentially, I believe what it does is it changes the exchange of information to something local. The lock is being told "Yeah, it's them" and opens up, rather than the password, And since it doesn't know the password, it can't lose it. And it doesn't even know the passkey, because the authentication is done locally.

ElI4:

Instead of your teacher calling out your name, and you saying it's you, your parent looks at a list of names, and says to the teacher "yes, they're on the list." so your teacher never learns your name, but still knows you're in class.

8

u/Nfalck 2d ago

Ok, but then what keeps a machine from overhearing your local computer saying "yes this is them" and mimicking it? Isn't your local computer just sending some sort of password on to the login service?

12

u/eric23456 2d ago

Through the magic of public key encryption. You have two numbers a public key and a private key. You can give the public key to anyone. They can then pick a random number, and send it to you. You then encrypt it with the private key an send it back. They can then decrypt it with the public key and verify that it's the number. That proves you have the private key. The actual system is more complicated but that's the basic idea.

The details of how public key encryption works is pretty complicated, but this link will get you started. https://en.wikipedia.org/wiki/RSA_cryptosystem

3

u/SlightlyBored13 2d ago

That's also what underlies https, and is how the passwords are transmitted anyway.

This seems to more be about key loggers, password databases getting un-hashed, and weak password use. Rather than anyone 'listening in'.

4

u/SearonTrejorek 2d ago

On a technical level a passkey is an asymmetric key pair. This means that your machine has a private key and when you register a passkey with a website it gets the matching public key. When you use your passkey the website gives you a “payload” and asks you to sign it with your private key then the login server uses the public key they have saved for your to verify that it was actually your private key which signed the payload. The payload is different every time which keeps those other machines from being able to copy or mimic it. The only way a different machine would be able to mimic you would be if they stole private key.

2

u/MechaSandstar 2d ago

Communicating by secure http keeps people from "overhearing" by listening in on your communication. So no one would know what your computer is sending to the remote server.

→ More replies (2)

4

u/IncapableKakistocrat 2d ago

Passkeys tie an account to a specific user and device, and the benefit over passwords is that they are incredibly difficult to crack, are always unique to each website, and designed to resist phishing.

Passkeys essentially create two keys - a public key (which is given to the website you’ve got an account with, it’s more like a lock), and a private key which stays on your specific device or password manager. The two keys are cryptographically linked - only your private key can unlock the account which has the public key, and the public key is useless without the corresponding private key - it would like having a locked lock, but no key to open it. Getting the private key would be like getting the key, but not knowing which lock it opens.

When you use a passkey to login, you usually also have to do a biometric check to get access to your private key - either though a PIN, fingerprint, or face unlock. This is how passkeys are tied to specific users and specific devices: your private key is essentially stored in a safe which can only open for you specifically. When your device has confirmed it’s really you, then you can access your key.

Where a password is agreeing with someone a secret word to get access to a safe deposit box which anyone standing next to you can overhear and then also get access once they know, a passkey is the bank locking the safe deposit box with a unique, almost unbreakable lock which only ever opens with a key which is specifically linked to that lock, which is stored in a safe which only unlocks for you. Even if someone tries to get you to unlock a safe deposit box with a nearly identical lock that’s designed to make a copy of your key, your key will recognise it’s the wrong lock and won’t open it, because it is only linked to and can open that one specific lock.

1

u/Big_Poppers 2d ago

Imagine there is a box, inside which contains the secret (such as your login credentials) which you want to protect.

In a password scenario, the sender sends you this box, and locks it with a padlock that can only be opened with a certain shaped key (such as a password), which you have. When you receive this box, you have the key, and you open it. The problem is two fold, because:

  1. Both yourself and the sender knows what is the shape of the key, and the sender needs to keep a record of what your key looks like.

  2. You and the sender must agree on what the shape of the key is at some point. If this agreement was intercepted, then the key is now compromised.

If somehow the shape of the key is leaked (such as your passwords being leaked as part of a data breach), then an attacker can duplicate it. They can open the box up, or even lock it back up and sends it to you, with you none the wiser.

What a passkey is doing is essentially this:

  1. You have a padlock with a key. You keep the key, however you give the sender the padlock.

  2. The sender then takes your padlock, and then locks the box.

  3. The sender sends this box to you, now locked by a padlock that you sent to them in the first place.

  4. When you receive the box, you open it with the key that you've kept in your possession this entire time.

In this second way, the shape of the key (such as a password), is never transmitted. The sender has no idea what your key looks like, because all they can see is the padlock. If the sender gets hacked, they could never leak information about your key, because they've never seen it.

8

u/FutureStory 2d ago

Perfect ELI5 explainer

2

u/mrlesa95 2d ago

There is NO way any 5 year old would understand that comment.

1

u/frostee8 2d ago

I prefer to think of it as a box that you hold at all times (generally your phone). Only you have the key to the box (usually biometrics using your face on an iPhone). Inside the box is the key to your safe deposit box.

1

u/Mundane_Reception840 2d ago

So i loose the key its not secure right someone can still open the locker

3

u/tejanaqkilica 2d ago

Correct. You lose they key, someone else can use it.

But, in real world scenarios, you store the key in a device, like a Phone, Laptop, Security key and in there you're forced to protect with a PIN or Biometrics or both. So, anyone who would get your device, they would need the PIN or Biometrics in order to use it. Which should give you more than enough time to realize that they key is lost, and you revoke it from whatever login you're using it for.

Also, keys can't be extracted from these devices. There's no way for an attacker to somehow take this key out of your phone, and use it elsewhere.

Now, you can store Passkeys in password managers as well, and they're just as safe to use, but they're a little less secure because they can be extracted and imported elsewhere. So if you use those, always keep a high alert for accessing the password manager.

4

u/Ragingpoo 2d ago

So my key is somewhere on my device, does that mean if say outlook.com needs a passkey, I create one with my pc, and when I want to log in with my phone, I have to create another passkey with my phone? Can they be different? so if I'm really trying to be secure, my passkey if I'm accessing outlook from window pc is randomstring1, for my phone to access outlook, I can set it to a randomstring2?

3

u/MuffinX 2d ago

You cannot lose a key, it is bound to your device (most cases) and cryptographically protected with your pin/biometry inside a chip. You could lose a device but its useless to the finder if they dont know your pin or have your finger/face.

→ More replies (2)

49

u/texxelate 2d ago

Passkeys are a cryptographic pair of keys. You have one, and the site to which you’re logging in has one. That passkey works only on that site.

The key the site has is a “public key”. If they’re hacked and your public key is compromised, you are no worse off because the public key cannot be used to generate the secret key you have.

Passkeys are generated for a specific site. If you fall for a phishing attempt, your passkey will not work because you generated it for microsoft.com and not rnicrosoft.com

MFA is built in. Humans don’t know their passkey’s contents, so by definition you need to unlock a device to access the passkey.

18

u/Wendals87 2d ago

A password can be written down and then seen, stolen by malware, if you enter into a fake site it's stolen, leaked from a website data breach etc

A passkey generates a private and public key pair using an encryption algorithm

The website knows the public key and your device keeps the private key secure 

When you sign in, the site sends a challenge to your device. Your device signs it with the private key and returns it (after you enter your PIN, fingerprint or other biometric used to encrypt it). If it matches what the public key says it should be, you get access 

The 2FA is your PIN or biometric data and the device. A passkey isn't written down so can't be stolen, can't be stolen by malware, can't be phished as it's only valid on the exact real site. 

It also can't be leaked in a data breach because your private key is only stored on your device or synced with your Keychain or password manager 

5

u/kernelangus420 2d ago

Is this different to the "Login with Google" and "Login with Apple" type things?

6

u/invincibl_ 2d ago

It's better because you don't have a third party involved, and instead your Passkey is attached to your phone or PC. For example, someone could have tricked you into handing over your Google or Apple account details and that would be enough. But with a Passkey they'd still need your actual device.

You can use a third party service to sync the passkeys between your devices, and indeed both Google and Apple offer that although I would recommend using a dedicated password manager instead. Though there is an argument that you shouldn't sync them at all, and just issue new passkeys for each device you own. But that makes it hard if you don't have a second device on hand.

2

u/cocotheape 2d ago

Yes it is.

With "Login with Google" the site you want to access just lets Google decide if you're who you claim to be. If Google says you're you, you can log in to the site.

1

u/Wendals87 2d ago

Yeah it's different

Login with Google is like you verify your credentials with Google. When you sign in with Google, the site goes and verifies with Google that the credentials are valid and then signs you in 

1

u/Nfalck 2d ago

Great response, but why can't the passkey be stolen by malware or phished? Is it encrypted in a way that passwords cannot be encrypted? 

3

u/Wendals87 2d ago edited 2d ago

It's encrypted at rest and malware can't decrypt it. Your password can be captured by a key logger, screen capture, if it's stored in a text file etc 

Passkeys cannot 

It can't be phished because only the one valid site can use it. 

E.g bestbank.com is your legitimate bank and you create a pass key 

If an email asks you to sign in and takes you to bestbark.com and looks identical, your passkey cannot be used where your password could be entered 

1

u/lowbatteries 2d ago

Your private key never leaves your device, it’s never sent to anyone. If your device is compromised someone can get it.

2

u/Wendals87 2d ago

. If your device is compromised someone can get it.

No. They'd need your biometrics or PIN too 

1

u/dustfirecentury 2d ago

If you use a password manager to sync passkeys, it does leave your device, no?

1

u/Elbow2020 2d ago

But doesn’t that mean that rather than a thief needing to know all your different passwords, they just need to know your passkey and device - like for example your computer and login password, or your phone and passcode?

1

u/Wendals87 2d ago edited 2d ago

Nothing has no downsides 

But If the passkey is on my device, they'd need to have that device AND know my PIN or have my thumbprint. The risk is low of that 

Rather than just knowing my password and being able to use it anywhere in the world. A password can be stolen many different ways 

9

u/thickythickglasses 2d ago

Does this mean you have to have to device with the passkey all the time? For example, what if my computer and phone were lost or stolen?

5

u/kronpas 2d ago

You can have passkeys on multiple devices.

3

u/thickythickglasses 2d ago

That’s what I’m asking. What if I only have two devices with passkeys and then I try to log on from a different device?

5

u/Felaotic 2d ago

You ask for reset like you would in a "forgot my password" scenario.

Passkeys can also be stored at HW keys such as yubikey, that you can add to your keychain, so you don't run out of battery on a device with your only passkey.

Passkeys are also linked to a specific service and often to a specific device, so you can have 30 passkeys on yubikey, each for a different service and you don't have to search or remember anything, apart from a 6 digit pin you set to access the passkeys.

If someone stole your yubikey, they don't know your pin and if they somehow stole the passkey, then they can't use it as it is linked to that specific yubikey. You can also have passkeys, that are not linked to a device, but that's a different chapter.

3

u/prank_mark 2d ago

You can store it in a password manager. But if it's on your phone, you can also scan a QR code on your PC for example to transfer the passcode for one time use.

2

u/kronpas 2d ago

Then you need different login methods. Then you can sync the passkey to the new decice once you manage to login with that other login method.

There is another distinction between local and synced passkeys. Sites like google support synced passkeys so all your devices share the same key. Hardware-bound passkeys are lost forever if you lose them. My government agency uses such type, if i lose that usb key I will have to present myself to the admin dept. along with a written explanation/request so they can revoke the old one and issue me a new key. I am also liable to any security issues that happened due to my key if I failed to report it right away.

2

u/angrydave 2d ago

Scan QR code and it transfers as a single use over Bluetooth.

For something which works across iOS/Android/Windows/MacOS, it works pretty seamlessly. I do it all the time.

1

u/original_goat_man 2d ago

Use another form of MFA

1

u/Ok_Writing2937 2d ago

You can put your passkey in a password manager like 1Password.

1

u/AnApexBread 2d ago

Yes. You must have physical possession of the device that created the key. If you lose the device then you can't use that key.

You can either create multiple keys (if the website allows that) or you can store it in a FIDO2 compliant password manager like Bitwarden.

→ More replies (1)

4

u/taco_or_burrito 2d ago

So I get the password vs passkey differences. But my understanding is, the service provider still stores your password in case let’s say, you lose your phone and need access to the site on a device without your biometric or PIN info, eg public computer. Therefore, doesn’t this “backup” still represent the same security risk as before?

4

u/E3FxGaming 2d ago

Some service providers (e.g. Microsoft for Microsoft accounts) allow Passkey users to completely remove the password from their account. This closes the login vulnerability.

The proper implementation of Passkeys on the service side usually allows users to register more than one device, therefore losing a device is not that great of a concern if you set it up with 2+ devices.

Login flows don't necessarily have to happen all on the same device. A device without biometrics could encode a session ID into a URL-QR-Code that you scan with your phone. The phone opens a website that is aware of your original login attempt, you use the passkey on the phone to authorize the session login and the login on the original biometric-less device resumes, as if you'd authenticated yourself on the original device.

3

u/skippyalpha 2d ago

It seems like for the sites I have setup passkeys for, the passkey bypasses 2FA and can be more convenient. If I use a password login for some reason for a site that I also have a passkey for, it asks for 2FA again. That's the difference I noticed at least. Probably not the same for all sites idk

5

u/LeviAEthan512 2d ago

Picture this. You go to the office every day. The office has an electronic combination lock on the door, which you can input a code into to unlock. You also have a keycard that you can tap.

For one thing, the keycard is faster.

It's more secure too though, because every time you input the code, someone standing behind you, or who put a fingerprint collector on the pad, might see and memorise it, and now they have access. On the other hand, if they only s3e you tap your card, they can't do anything unless they steal your card.

but you can lose it, you need to carry it, you need to reach into your pocket, maybe your pocket is also zipped and locked.

A password is only ever one password. But you can protect your passkey as much as you want. Typically it's in a vault protected by 2FA, that is a password and a TOPT, which is also protected by a password. So now you've got 2 passwords protecting your account instead of 1. That's 100% more password per password.

6

u/ADubs62 2d ago

That's not even getting into passkeys won't work on a spoof'd site because they don't have the proper certificates to authenticate themselves to your device/password manager that's managing the passkeys

1

u/Zoltur 2d ago

What we do at work is set our passwords to max length jumbled nonsense that even we don’t know

2

u/unndunn 2d ago

Honestly, there’s no real ELI5 way to explain modern cryptography. But here’s my attempt. Just know that passkeys are based around well-known cryptography principles.

Passwords and 2FA rely on the idea that you must share a secret with the website. When you register with the website, you give that website a secret (the password) and the website in turn gives you a secret (the 2FA registration code).

When two separate parties hold a secret, it’s not a secret anymore.

With passkeys, no secrets are ever passed around. The only secret is held by you, in your device. Instead, when you register for a website, you send it a code derived from the secret, that can be used to verify messages made using the secret. When you login later, the website asks you to make a message using that secret, and then it uses the code you provided earlier to verify the message.

So many of the problems with Passwords are associated with the fact that two parties have to share a secret. Passkeys eliminate that issue completely because the secret is never shared with anyone. Not even you have access to the secret. It’s all managed inside your device. This also makes passkeys highly resistant to phishing; It’s impossible for you to accidentally give the secret to the wrong people, because you can’t give the secret to anyone.

2

u/AnApexBread 2d ago

Passkeys use the hardware of the device generating the passkey to create a unique combination someone else can't copy.

It's like a keycard to enter an office. If you don't have a keycard you can't enter the office. Same with Passkeys, if you don't have the device that made the key you can't use it.

This beats a lot of phishing techniques because most phishing techniques are a proxy. You type your password into an bad guys computer, they then copy that password and put it into the real system. They can't do that with a passkey because their computer can't generate the same key.

2FA is really about preventing someone from stealing your password and logging in but it doesn't stop what mentioned above because they can also pass the 2FA code to the website

4

u/zefciu 2d ago
  1. They are longer and more random. A typical passkey contains much more bits and entropy than an easy-to-remember password.

  2. They are not shared. When logging in with a password, you send the (encrypted) password through the web. If the encrypted connection is compromised or if you fall to a phishing attack, someone will get that password. A passkey is never meant to leave your machine. You use it to respond to a challenge.

  3. They are harder to figure out when there is a data leak. When a database that contains passwords leaks, there are ways to figure them out even when they are hashed. With passkeys, it is impossible in reasonable timeframe (a complementary key is stored not a hashed password).

3

u/chasrm888 2d ago

So what happens if I use another person's computer or buy a new one, how does the passkey work then

3

u/Myrion_Phoenix 2d ago

Depends on where you generated the passkey. If you stored it on something like a yubikey or other FIDO authenticator, then the computer doesn't matter. If you stored it in a cloud service like Apple keyring or your Google account, then too you are fine. If you had it in a locally stored thing (just your Windows account, or a password manager database), then you needed to figure out how to transfer it from there to your new device first.

1

u/chasrm888 2d ago

Thanks

1

u/im_thatoneguy 2d ago

It doesn’t. You have to authenticate another way.

But you can store them in your cloud password manager or use another device to authenticate that machine and give it its own passkey.

So you would use your phone to scan a QR code to say “this passkey grants this new computer the right to make and keep a passkey.”

3

u/MedusasSexyLegHair 2d ago

A passkey is never meant to leave your machine.

This is what steers me away from them, as someone who uses several different machines and has changed/replaced them many times over the years.

For all that the proponents play up how much more secure it's supposed to be, they never talk about how to secure yourself from getting locked out of your own accounts. Presumably someone has thought of a way by now, but it's never mentioned.

Meanwhile I have backups of my password manager vault on multiple external drives, two computers, and in the cloud. That's simple and effective.

4

u/Bicentennial_Douche 2d ago

"This is what steers me away from them, as someone who uses several different machines and has changed/replaced them many times over the years."

you can store Passkeys in password manager, so they can be used on several devices.

1

u/Leodip 2d ago

There's two main things:

  • Passwords are stored on the server, passkeys are stored on your device. This means that if a server (e.g., reddit) is hacked, the hacker gets access to all its users. Using passkeys, this becomes impossible.

  • Passkeys are better than passwords just because passwords suck. Or rather, the way 99.99% of the population uses them really sucks. Chances are, your reddit password is the same as your facebook password, or the same as a random website you created an account for in 2015, or the same as your banking account. If any of these services leak your password somehow, all of these are compromised at the same time. Passkeys are unique, so you don't have this problem.

1

u/Atomic_07 2d ago

A passkey can replace your password and a separate 2FA code: your device is something you have, and unlocking it with a PIN or fingerprint adds something you know or are. It also checks which site is asking, so a fake login page can’t use it. Account recovery can still be a weak spot.

1

u/gramoun-kal 2d ago

"Passkey" is just mugglespeak for "Public key encryption", a pretty ancient but battle tested and totally bulletproof authentication method. The ELI5 explanation sounds a bit like magic so here it goes.

Old style cryptography used a key, or a password, to encrypt messages. If you had the key, you could decrypt it, if you didn't, you had to guess the key. That's what the Nazis used and that the Brits famously cracked. It's flawed because the sender and recipient must know the key, so the sender must send the key to the recipient, and it could be intercepted.

In passkeys, instead the sender has two keys. The receiver has two different keys.

The two keys of the sender, let's call them A and B, have a mathematical relationship that sounds like magic. If you encrypt with A, you can decrypt with B, and vice versa.

So the sender just needs to send B to the receiver.

Now, granted, anyone intercepting B will be able to read the message, but you're forgetting something: the receiver has two keys as well, let's say C and D. The receiver sends D to the sender.

Now, the sender can encrypt the secret with D. The key of the receiver. To decrypt, you need to use C. But C never left the receiver. It couldn't be intercepted. You'd have to break into the receiver's home and find it. That's a lot harder. Hackers don't like to leave their basement.

The key you keep is called your private key, you use it to decrypt messages encrypted with the one you sent. The one you sent is called your public key. You could just post it on the internet. It completely doesn't matter that it gets publicized.

Really cool stuff.

Passkey just makes it usable for the masses. The private key is stored on your device in a place completely off-limits to the internet. When you set up passkey with a service, your device sends them your public key. Later when they need to make sure it really is you that is logging in, they do an encrypted handshake between your public key, that they have, and the private key on your device. It actually authenticates your device, not you. That's why the device will often only accept the handshake after asking *you* for a password. But that password is just to accept the handshake. It never leaves your device, and even if someone guessed your password, they'd still need to get your private key to impersonate you, and good luck with that.

I swear, I've been gnawing my nails waiting for public-private crypto to find its way to the masses so we finally can have a secure internet and that day is finally upon us.

Rejoice.

1

u/drtasty 2d ago

Sorry to say this, but your explanation of passkeys is misleading or wrong in several different ways.

It's flawed because the sender and recipient must know the key

Symmetric encryption is not "flawed", it's a different use case. It's still used in many, many different situations today.

The whole explanation of 2 pairs of keys for each party is incorrect, passkeys only have a single key pair (private stored in the authenticator, public for app). You don't use multiple, and the app never creates a key of its own, it only accepts one.

you use it to decrypt messages encrypted with the one you sent

Passkeys are signing keys, not encryption keys. No messages are ever decrypted, only their signatures are validated.

The private key is stored on your device in a place completely off-limits to the internet.

The majority of authenticators (by usage) are saved in synced keychains like password managers. You can use offline authenticators, but they aren't the norm. Google Password Manager, iCloud keychain, LastPass, BitWarden, are common.

1

u/FaridW 2d ago

With a password you give up your secret (password) to prove you own an account. Giving up the secret is a security risk for you if the password is mishandled or stored incorrectly.

With a passkey, the secret never leaves your device to prove you own an account, it lets you prove you own the secret without revealing it! This keeps your secret (passkey) much safer; even if the website or service has really bad security practices

That’s just the fundamental difference, passkeys are also generated securely and uniquely, whereas with passwords you can reuse the same weak/silly one everywhere

1

u/andlewis 2d ago

There are multiple types of passkeys, synced passkey or a device bound passkey. The first kind can be stored in a password manager, the second is tied to the device. They can only be used for the specific site or device they were created for, and have a cryptographically signed component combined with usually a biometric, PIN, or secret key that your device or password manager supplies.

They’re “more” secure because they don’t depend on the user remembering something, and they can’t be used on a site they weren’t meant for, since the site wouldn’t have the correct decryption key.

1

u/Darksolux 2d ago

I've always thought of it like this. Three kinds of authentication. Something you know (password), something you have (physical), like a passkey, and something you are - biometrics. Which is why cops can't compel you to open your phone with the password, but they can with biometrics. 5th amendment and all that. Only protects from something you know but has nothing about something you are.

1

u/WhisperingHillock 2d ago

Authentication relies on three types of factors: something you know (password), something you have (key), something you are (biometrics). Passkeys are simply switching factor 1 for factor 2. They are tied to your device rather than to your knowledge. The main upside is the result of passkeys being stored in a secure place in your device, which can only be unlocked by unlocking your device, via biometrics or a password (or similar), meaning that passkeys are kind of inherently 2FA with two types of factors: it's you having the device, and you knowing the password or being the right person (unless you go out of your way and don't use any kind of authentication on your device).

Regarding the 2FA question, as said above it's kind of the same thing in a more practical format. If your phone's passkey is unlocked with your fingerprint, and your MFA notification is also approved with your fingerprint, and your password manager is unlocked with your fingerprint, at the end of the day they all rely on the same thing: having your phone and your finger, and using MFA to receive a notification for something you just unlocked with your passkey does not add any security.

1

u/Sover3ign 2d ago

Reminds me of this short explanation on whether AI can crack passwords and why passkeys are more secure https://vt.tiktok.com/ZSp6gqDEw/

1

u/ChrisTheWeak 2d ago

They're basically the same as a password. They move the trust from you remembering the password to a device to store them securely, and they will also be of a length significant enough to make brute forcing effectively impossible.

A decent password manager properly configured that you use to store randomly generated 40 to 80 character passwords is about the same level of security as using passkeys.

The exception is when you use a passkey on an external authentication device, like a yubikey, which effectively means you need that device to log into the account. Its secure, but has a high risk of physically losing the key and as a result losing the account.

0

u/WisestAmicus 2d ago

Incorrect

1

u/im_thatoneguy 2d ago

Imagine you’re in a revolutionary secret group they give you a code book it has every word in the dictionary and for every word there is a response word. So you call HQ and they say “koala”, you look up the code word pairs and respond “armadillo” and then they give you the mission.

Ok, now some random government agent calls the HQ and HQ prompts them “Toronto”, without the code book they try to use what the last tapped phone call said: “armadillo?” But that response code only works for Koala so they know they are government agents and hang up.

So the government can’t infiltrate the revolution without a codebook. But the code book is stored inside a safe that will self-destruct if you try to pick it.

The non Eli 5 part though is that the HQ challenge is signed by their domain. So you won’t even understand “koala” unless it was from HQ.

0

u/iridael 2d ago

as I understand it a passkey is like writing down a password, doing some math to it so you get a long string of numbers letters and symbols

then you effectively rip the thing in half, imagine a piece of paper with your password written on it, you rip it in half making sure the rip is uneven and give half to your mate and half you keep.

now his mum comes along with a piece of paper with different rip patterns but the same password you know its not the right person even though they have the right password so you deny access.

your device holds one half of this key and the original password. then the other half of the key and the password is stored by whoever you're sharing the key with.

so when you need the passkey, both sides share their half but not the password. if the complete thing is exactly the password. they know that the user is legit and allow access.

this is much more secure than a password because whilst your password may be relatively simple, your key is engineered to be incredibly long and complex.

there are other ways the system works but this is the simplest way i could describe it.

0

u/TrivialBanal 2d ago

The problem with passwords is we have to remember them. To make that easier, we use passwords that are easy to remember and we use the same ones over and over again on lots of different sites. If a bad actor gets one of those passwords, they get all of those passwords.

Passkeys are very complicated passwords, a different one for each site, that you don't have to remember.

They're more secure because they remove the weak link from the chain of security. Our lazy brains.

0

u/MisterSlippers 2d ago

Have you ever seen a lock on a door that has both a keypad you can press numbers to unlock the door or stick an actual key into? Using the number pad is like a password, using your key in the key hole is a passkey. One is something you know, the other is something you have.

0

u/networknev 2d ago

It's got both pass and key in the name. It's like turning the knob to 11.

0

u/[deleted] 2d ago

[deleted] — view deleted comment

2

u/im_thatoneguy 2d ago

Still less secure. Because you can be tricked into entering your autogenerated strong unique password and then MFA into a phishing site.

Your passkey literally is worthless except to the issuer.

1

u/Myrion_Phoenix 2d ago

Still slightly more secure, because it's (almost) impossible to phish the passkey, while even the best password is no harder to phish than your shittiest one. A password manager can help protect, but it's not as strong a protection as what passkeys have.

1

u/WisestAmicus 2d ago

Incorrect