4 ms·
> use this to tether and lock you in to their platform. You could say this about Google's proprietary authenticator app in the past, but now that they support
by lxgr 4y ago
> use this to tether and lock you in to their platform.
You could say this about Google's proprietary authenticator app in the past, but now that they support Passkeys, arguably the opposite is true.
Importantly, you can now (with FIDO CTAP 2.2 and tunnel services [1]) use an out-of-platform Passkey to log into your account cross-device, e.g. you can use an iOS Passkey to log into an account on a Windows Chrome instance via QR/Bluetooth.
There's absolutely nothing stopping you from providing your own implementation as long as it complies with the "hybrid transports" part of FIDO CTAP 2.2.
[1] https://fidoalliance.org/specs/fido-v2.2-rd-20230321/fido-client-to-authenticator-protocol-v2.2-rd-20230321.html#sctn-hybrid https://fidoalliance.org/specs/fido-v2.2-rd-20230321/fido-cl...
- dcow 4y agoYou're suggesting that using a tunnel service is the recommended way to be a platform agnostic backend. But that doesn't cover the scenario where your password manager is running on the same device as the one where the user is performing the login, and all the UX/UI refers to using a phone to scan the QR code. I guess you could snag the QR code using platform accessibility features, but that's a real silly hack. Just let me advertise some mDNS service record for "authenticator" and require me to advertise a pubkey and let the user select/allow me once and remember the decision until the pubkey changes so that I'm trusted backend without the QR scanning rigamarole.
- lxgr 4y ago> the scenario where your password manager is running on the same device as the one where the user is performing the login Android will provide an API for that scenario (i.e. on-device third-party authenticators) in the near future [1]. Hopefully, iOS will do the same. [1] https://developers.google.com/identity/passkeys/supported-environments https://developers.google.com/identity/passkeys/supported-en...
- dcow 4y agoYes, I'm waiting patiently in the wings. Sadly when I asked Apple's Passkey team about supporting this, they said it wasn't on the roadmap (though they carefully didn't say never, it still doesn't instill much hope). Once this missing piece becomes a required part of the standard, I'll stop holding my breath and get super excited about passkeys.
- michaelt 4y agoThe article says "Instead, passkeys let users sign in to apps and sites the same way they unlock their devices: with a fingerprint, a face scan or a screen lock PIN." Does that not rather imply that, if I log in with faceid on an iphone, my login will be tied to my ability to faceid on an iphone, and hence only available on iphones and macs? As a user, that's sounding a lot like platform lock-in to me. And as a developer, if I want a way for users to log in without a password, and I don't mind that login mechanism being reliant on the user's account with apple / google / microsoft - wouldn't I just add a 'log in with apple / google / microsoft' button to my login page?
- voxic11 4y agoNo passkeys are just normal private keys. You can store those private keys in a particular platform's secure key store which on phones can be decrypted/made usable when you unlock the device. But there is nothing stopping you from transferring these keys to a different device if you wish.
- lxgr 4y agoTrue, Passkeys are private keys at heart, but relying parties can verify whether they are stored in software or hardware by requesting/requiring authenticator attestation when they are created.
- dcow 4y agoAnd certain hardware from certain platform vendors doesn't allow exfiltration of private key material. Though I don't think this can be specified by the relying party so that's how Apple stores all keys in keychai. I sincerely hope it remains best practice for relying parties to not require/use the platform attestation feature to lock users onto "trusted" platforms.
- lxgr 4y agoDevice binding can be required by relying parties! They can just refuse to accept credentials without attestation statements signed by a trusted party. My government e-signature service does that: I can’t even use a Yubikey, ironically, because that’s not "FIDO level 2 certified". I had to buy a more or less completely unknown brand instead (of which a government affiliate is apparently the exclusive reseller in my country…)
- onlypositive 4y agoCan I store the keys in bitwarden or am I stuck using google chrome to access this or whatever Mozilla cooks up? I can't rely on retaining access to my Google account for logging into things.
- lxgr 4y agoOn Android, there will supposedly be an API for third-party Passkey implementations soon: https://developers.google.com/identity/passkeys/supported-environments https://developers.google.com/identity/passkeys/supported-en... 1Password has already announced their intention to use this once ready. I really hope iOS will provide something similar soon.
- yepguy 4y agoNot now, but soon. Bitwarden's public statements over the past year, and their acquisition of passwordless.dev, would seem to indicate that they're working very hard on adding passkey support.
- sdfghswe 4y ago> You could say this about Google's proprietary authenticator app in the past There's many implementations of OTP. I've never used google's and I've been fine.