3 ms·
> The only way passkeys make sense is in terms of vendor lock in. This is what I've figured as well, and even if my password manager claims "eventually we'll s
by diggan 1y ago
> The only way passkeys make sense is in terms of vendor lock in.
This is what I've figured as well, and even if my password manager claims "eventually we'll support it, once it's available" (https://blog.1password.com/fido-alliance-import-export-passkeys-draft-specs/ https://blog.1password.com/fido-alliance-import-export-passk...), I've been putting it off until the implementation is actually in place.
But the question is when that'll be. Last I've heard about the whole "Risk of lock-in from export blocking" is:
> The general vibe is supportive and language has been added to this effect, though it looks like we haven't done a public working draft in some time so I don't think that's externally visible yet. Also usual caveats about in-progress work subject to change.
https://github.com/fido-alliance/credential-exchange-feedback/issues/24#issuecomment-2905416990 https://github.com/fido-alliance/credential-exchange-feedbac...
I guess time will tell. But for now, considering the history of lock-in on the web, it's best to stay away from Passkeys for now, until they figure out a proper way of avoiding it.
- signal11 1y ago1Password are working with Microsoft to integrate more with Windows’ passkey APIs. The real test will be, how easy is it to move passkeys from say 1Password to Keepass XC (open source). It’s on my todo list. For now, 1P’s passkey support appears to work quite well with all the sites I’ve tried. I’ve got multiple devices (Linuxes, macOS, Windows) and passkeys just work. I like the fact that 1P is cross platform, but after all it too is proprietary.
- diggan 1y ago> how easy is it to move passkeys from say 1Password to Keepass XC (open source). It’s on my todo list. AFAIK, there is no export from 1Password with Passkeys yet, so maybe better to put it in your calendar to check back in 6 months or so. > passkeys just work Yeah, I'm not doubting that, but I cannot reasonable base my core authentication on something that locks me to one service, that just feels to irresponsible. Hence the wait for proper import/export before spending any time on this :)
- jgalt212 1y agoTruth. With passwords, you don't even need a service open or closed. You can just write them down on an air gapped piece of paper.
- trollbridge 1y agoBitwarden is the one vendor that doesn’t do lock in (since you can export your passkeys). Which also means you can back them up. The rest of the platforms give you zero ability to export or back up your passkeys, which makes them worse than useless.
- Longhanks 1y agoApple also announced passkey import and export is coming this fall with iOS 26 (and their other OSes): https://developer.apple.com/videos/play/wwdc2025/279/ https://developer.apple.com/videos/play/wwdc2025/279/
- diggan 1y ago> We'll explore key updates including [...] and the secure import/export of passkeys Have they shared any details about if this is actually cross-provider/platform import/export? I feel like if Apple doesn't outright share those details, they're talking about import/export within the Apple ecosystem.
- dcow 1y agoNo, in this case it is actually an industry standard: https://fidoalliance.org/specifications-credential-exchange-specifications/ https://fidoalliance.org/specifications-credential-exchange-...
- diggan 1y agoNothing of the info Apple published so far seems to indicate that they'll implement that. And again, based on the track record of Apple, feels unlikely they won't implement something on their own.
- tzs 1y agoFrom the video cited upthread: "This transfer uses a data schema that was built in collaboration with the members of the FIDO Alliance. It standardizes the data format for passkeys, passwords, verification codes, and more data types"