3 ms·
I want to manage passkeys myself. I don't want to use iCloud Keychain sync, and I don't want to use 1Password. This is a non-negotiable requirement for me. Othe
by lapcat 4y ago
I want to manage passkeys myself. I don't want to use iCloud Keychain sync, and I don't want to use 1Password. This is a non-negotiable requirement for me. Other than that, I'm fine with the idea.
- idiotsecant 4y agoThis is actually already built in the much maligned 'web3' that everyone loves to hate ( even if it deserves it sometimes) Signing into something with your ethereum wallet works well, you get to pick how you store your keys and sign (brain, paper, encrypted file, hardware wallet) and if you use something like argent you can even have social password recovery if you want it for low impact applications. It's so awesome and it just works. I wish more things used it.
- smoldesu 4y agoIt's also built-in to GPG, which has been around since the mid-90s. The Blockchain is a completely unnecessary component for this sort of cryptosystem.
- blep_ 4y agoAlas, the blockchain people are the ones who made it popular. I would love to sign into things with GPG keys, but I have never seen a single thing that supports it.
- smoldesu 4y agoIs it popular, though? Even now, the number of Metamask-enabled applications feels tiny relative to the provenience of GPG signing in the world of software.
- idiotsecant 4y agoNo, while it's popular in certain spheres it's decidedly unpopular in general. It is, however, orders of magnitude more popular than GPG for website sign-in.
- smoldesu 4y agoRight. If we're talking about practical usage though, GPG sees more widespread adoption than blockchain auth. Part of it is because it's older, but also because it's simpler and more redundant.
- tmpfs 4y agoTo clarify here, this is just public key cryptography using ECDSA signing keys to verify an identity. Whilst it is blockchain-adjacent it does not use a blockchain for identity verification, it just checks the owner has access to a particular private key.
- g_p 4y agoTo add to this, I also want the ability to move "ecosystem" - passkeys are "platform-backed", meaning Chrome on iOS is "iOS" as far as passkeys are concerned, and you are stuck in the iOS keychain. I want to see proper migration paths between iOS, Android, Linux, Windows, Mac, BSD etc - so that there is no platform lock-in or inertia that prevents you leaving one platform for another, and quickly (in under 30 seconds) moving everything across. At a time when competition authorities are clamping down hard on platform dominance, self-preferencing and lock-in, passkeys risks becoming a pain point if there isn't proper, genuine, portability. I'm also not keen on the lack of self-sovereignty of passkeys as you suggest - this feels like a "by the back door" way to force everyone into using "Sign in with X" type federated login. When your cloud account is locked out by Google AI, you want to be able to sign in to your other services! People have already started to discover the risks of Oauth type login when their bigtech company locks them out.