3 ms·
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
by 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.