3 ms·
https://webauthn.wtf/how-it-works/support https://webauthn.wtf/how-it-works/support > WebAuthn is supported by a wide range of devices and platforms, including
by danShumway 3y ago
https://webauthn.wtf/how-it-works/support https://webauthn.wtf/how-it-works/support
> WebAuthn is supported by a wide range of devices and platforms, including desktop computers, laptops, smartphones, and tablets. Check out passkeys.dev for more information on device support and compatibility of passkeys across different devices.
And then the support table is at https://passkeys.dev/device-support https://passkeys.dev/device-support, via website that is maintained by members of the WebAuthn working group.
Still no real Linux support, general Linux is still not listed as a target for support, only Ubuntu. The most important support categories have no support planned according to the passkeys.dev website.
And no, FIDO hardware keys or cross-device authentication are not sufficient support, as this site itself admits:
> One option is to register passkeys on two devices: one that is carried for everyday use and another that is kept in a secure location as a backup. That solution is cumbersome, and most people are not going to bother.
If you only have a phone and a Linux desktop computer, it means that backup that's available immediately on multiple devices is going to be much more difficult.
Of course, the Passkeys.dev site is out of date; in theory 1Password can actually be used as a local provider on Linux (although I haven't tested it, so in before I'm wrong about that). 1Password is proprietary and doesn't allow export currently, but even so you'd think that the site would be updated. But nah, we'll just force everyone with questions to browse blogs and Twitter to get them answered. It's a fun scavenger hunt we're all doing where we try to figure out where the heck Passkeys can and can't be used.
----
Also no mention at all from either site about cross-ecosystem compatibility (ie, export/import); it's nice that passkey proponents have done a 180 from "ecosystem transfer is harmful and shouldn't be supported" to "of course we always intended to support ecosystem transfer and it's definitely coming" -- but again, would be nice to see anything at all official about that or a timeline. Why am I finding out about cross-ecosystem compatibility from Reddit posts, isn't there an alliance somewhere around here made up of some of the richest companies on earth that could help with messaging?
----
Passkeys have the potential to be great, but they are early development, they have heavy caveats, there are problems with the spec, and they are being recommended to people today even though there is no officially advertised Open implementation for local providers that works cross-platform (Bitwarden support hasn't launched yet, and I haven't been able to find another Open Source provider advertised through FIDO's certification program). So in their current state they are objectively, factually, vendor lock-in, even if that is intended to change in the future.
They shouldn't be recommended to ordinary users today, it is irresponsible for tech companies to be advertising them in a half-finished state.
----
This website appears to be a 3rd-party effort, so it's unreasonable to blame it for the problems that the actual FIDO Alliance has with messaging and communication and development priorities. The company that made this site very likely has no power to change anything about what the FIDO Alliance is doing.
And it's good to get more informative resources about Passkeys, I particularly appreciate clear developer guides around providers. So I don't want to make it sound like I'm complaining about the site; I'm happy that FusionAuth set this up. And FusionAuth is aiming this site primarily at developers, not users, so I'm not even mad about that.
But it's still kind of a band-aide over communication problems that the FIDO Alliance itself needs to address, and it papers over the reality that passkeys in their current form aren't ready for normal users yet. Stuff like export/import isn't optional; if I can't export keys from iCloud or Android, then passkeys are not ready for normal users.
- varjolintu 3y agoKeePassXC's Passkey implementation allows free import/export, and of course Linux is also supported: https://fosstodon.org/@keepassxc/111298602211286675 https://fosstodon.org/@keepassxc/111298602211286675
- danShumway 3y agoThis hasn't actually been released yet, it's just in the release branch. It was merged down less than 4 days ago. It comes with the following caveats: > What is not working / is missing / won't be implemented: > Some extensions are still missing (authentication doesn't support them at all, yet). > Support for Resident Key. > Support for triggering unlock from extension. > Support for root certificates. > Support for PIN/TouchID when authenticating. > What is not tested: > Support for Passkeys with Google/Apple and other common sites So... can anyone confirm to me whether the passkey implementation in KeePassXC actually works with any of the sites implementing passkeys? I'll be happy if it ends being great and works everywhere. But what should I take away about the spec that the developers who have implemented the spec in KeePassXC aren't certain whether it will work with every site that claims to support passkeys? I know it won't work with any site requesting hardware-bound keys: https://fosstodon.org/@keepassxc/111301312353785552 https://fosstodon.org/@keepassxc/111301312353785552 I'm happy for KeePassXC to add support, it's a big deal, but it seems pretty early to say, "see the Linux situation is solved now." I go back to the complaint about passkeys being recommended for people to use today, even though they're still kind-of half finished. This is on a release candidate branch, and we're already acting like Linux is just supported now. Never mind the fact that it's a partial implementation, never mind the fact that we have no idea if browsers like Chrome will allow KeePassXC to be treated as a platform provider without installing an additional extension to bypass the browser's built-in behavior. Never mind the fact that its import/export format only works with itself. Linux is supported now and you can export your keys, what's the problem? /s ---- And ignoring all of that, if Linux has support now, I would repeat: why do I need to find out about this on Mastodon? Seriously, the FIDO Alliance is made of the richest tech companies on the planet. Why is the official user-facing dev site -- a site maintained by W3C members and organizations -- giving incorrect information? Why are supported features, goals, and timelines being communicated entirely via social media?