5 ms·
Does this include a way for a technically-savvy user to 'repatriate' their passkeys into their own infrastructure? (i.e. If I want to be my own provider)
by rkagerer 2y ago
Does this include a way for a technically-savvy user to 'repatriate' their passkeys into their own infrastructure? (i.e. If I want to be my own provider)
- commandersaki 2y agoAt a minimum we will see if KeePass is a provider that is supported; they seem to be the only pw manager in town that respect user freedom.
- lovethevoid 2y agoKeepassXC already supports passkeys
- rprospero 2y agoI'm curious if you count Pass (https://www.passwordstore.org/ https://www.passwordstore.org/) as not being "in town" or if it has issues with user freedom that I'm ignorant of.
- commandersaki 2y agoEh I should’ve qualified with pw managers that support passkeys.
- ratorx 2y agoCan you not just set up a new passkey using a different provider (eg. Bitwarden)? It is a bit inconvenient, since it has to be done manually for every site.
- whatevaa 2y agoA bit is understatement. If this passkeys become widespread, we are talking about like 100 sites.
- ensignavenger 2y agoI have over 500 logins in my Bitwarden account right now. Many of those are not important in the least, but hundreds of them are.
- Jnr 2y agoIf you go for passkeys, start putting them in your own provider from the start? Vaultwarden is a nice option.
- HeatrayEnjoyer 2y agoThere shouldn't be. Secure enclaves aren't secure if they can be copied
- lucianbr 2y agoHow does this suddenly become a problem when as the user I want access to my keys, but it isn't a problem when corporations copy my keys between them, which is what this post is about?
- deleted 2y ago[deleted]
- jasonjayr 2y agoSecured against who?
- eikenberry 2y agoSo you are against this new spec becoming a standard then?
- benlivengood 2y agoThe exchange spec suggests that the sending secure enclave sends encrypted credentials to the receiving secure enclave; they're never unwrapped in public between 'trusting' enclaves; which enclaves will trust each other enough to perform the credential transfer is another question.
- noirscape 2y agoIn that case, the keys would be a non-starter. The overwhelming majority of tech requests relate to people forgetting their passwords and getting in trouble because the browser's password manager forgot the password itself. The reality is that the biggest pushers of Passkeys are the providers with the least amount of infrastructure stability. If you want people to get to use Passkeys, providing an exit tool from Google and Apple is a must, because both providers are godawful at not accidentally mushing up your data. That's not so important if all you're using their infrastructure for is a periodic backup/use it to transfer photos to your PC, but it's a problem for anything that has to be stored long-term.
- Terr_ 2y agoI would also be concerned about whether you can recover when a provider becomes unusable or hostile, and there is no cooperative migration path. That might be the company going bankrupt, a physical or digital disaster, geopolitical firewalls, or simply a Kafka-esque bureaucracy where your entire account has been deleted without appeal because the company decided it was easier than figuring out the truth behind some moderation issue.
- EasyMark 2y agoThat seems scary, I think I’d rather move them over one by one and delete the old passkey/2fa. I want to make it as hard as possible to keep them from being moveable as that’s one less attack point for hackers.
- deleted 2y ago[deleted]