3 ms·

> but if you're the target audience for passkeys This is the difference. With the big players pushing it, including Apple instructing developers on the best wa

by judge2020 4y ago

> but if you're the target audience for passkeys This is the difference. With the big players pushing it, including Apple instructing developers on the best way to integrate passkeys in their apps[0], it's going to overall shift more people from passwords to passkeys (especially when developers prioritize passkeys during signup). 0: https://developer.apple.com/documentation/authenticationservices/public-private_key_authentication/supporting_passkeys https://developer.apple.com/documentation/authenticationserv...

falcolas 4y ago
I have... doubts. Already webauthn isn't prompting for passkeys on Apple. Chrome wants a bluetooth connection out of the box, and firefox does its own internal auth path that doesn't involve the OS. Chrome and Edge on Windows are the only ones that prompt me for passkeys today (Firefox tries to use Windows for auth, which throws up a scary prompt).
- judge2020 4y ago
  I don't follow for these > Already webauthn isn't prompting for passkeys on Apple. It does for me on iOS, at least (and Safari on MacOS; other browsers don't use the native icloud passkeys, chrome has its own secret store). > Chrome wants a bluetooth connection out of the box, IIRC it works without it for on-device passkeys, but caBLE requires Bluetooth to facilitate proximity passkey connections if you want to use wireless webauthn.
  - falcolas 4y ago
    > other browsers don't use the native icloud passkeys, chrome has its own secret store > but caBLE requires Bluetooth to facilitate proximity passkey connections if you want to use wireless webauthn. And that's the problem. The lack of a cross browser/device/os standard. You can't create a secure authentication chain - let alone replace passwords - without standards that are broadly accepted; without broadly accepted standards. To do otherwise means you have to train your average Jack on 4 (or more) different ways to authenticate to one service. And the way they'll pick? Passwords. Because they know how to use passwords.

falcolas 4y ago

I have... doubts. Already webauthn isn't prompting for passkeys on Apple. Chrome wants a bluetooth connection out of the box, and firefox does its own internal auth path that doesn't involve the OS. Chrome and Edge on Windows are the only ones that prompt me for passkeys today (Firefox tries to use Windows for auth, which throws up a scary prompt).

judge2020 4y ago
I don't follow for these > Already webauthn isn't prompting for passkeys on Apple. It does for me on iOS, at least (and Safari on MacOS; other browsers don't use the native icloud passkeys, chrome has its own secret store). > Chrome wants a bluetooth connection out of the box, IIRC it works without it for on-device passkeys, but caBLE requires Bluetooth to facilitate proximity passkey connections if you want to use wireless webauthn.
- falcolas 4y ago
  > other browsers don't use the native icloud passkeys, chrome has its own secret store > but caBLE requires Bluetooth to facilitate proximity passkey connections if you want to use wireless webauthn. And that's the problem. The lack of a cross browser/device/os standard. You can't create a secure authentication chain - let alone replace passwords - without standards that are broadly accepted; without broadly accepted standards. To do otherwise means you have to train your average Jack on 4 (or more) different ways to authenticate to one service. And the way they'll pick? Passwords. Because they know how to use passwords.