this post was submitted on 11 Oct 2023
292 points (98.0% liked)
Technology
59329 readers
4564 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
From Ricky Mondello, who works on passkeys at Apple: “If it’s device-bound, it’s not a passkey”:
https://hachyderm.io/@rmondello/111188643228872151
That's a terrible take ... He's confusing "what it does and how it works" with "how you manage it".
It's like saying "don't call it a password if you write it down". It's confusing and unhelpful.
No it's literally in the spec. Passkeys are designed for cross device synchronization. You have to go out of your way to make it local only (or use a different webauthn spec like physical security keys)
They're just private keys. By nature you can copy them wherever you want. I guess I don't know why he's making that distinction at all.
The original spec is resident keys including TPM protected or hardware token protected keys designed to be impossible to copy. That's why there's a distinction.