3 ms·
This is a pretty cool scheme, but I'm not sure about the UX argument. The login flow itself is good UX, but it's arguably just the happy path, and now I'm respo
by ben0x539 9y ago
This is a pretty cool scheme, but I'm not sure about the UX argument. The login flow itself is good UX, but it's arguably just the happy path, and now I'm responsible for irreplaceable data on my device. My device might fall into a river, or a customs lockbox. I can mitigate that but then I'm doing manual secrets management work that "eh, I'll just trust my email provider" would have prevented.
- level3 9y agoIt seems like your device is completely replaceable in this scheme. The keypair is derived solely from the email address and the master password, so you can just generate the same keypair on a new device.
- homakov 9y agoExactly - everything can be derived from password. It's simplest backup strategy possible.
- ben0x539 9y agoAh, so it's like sharing one password for everything? Edit: Yeah, with the crucical difference that you don't need to worry about the server's user database getting leaked along with your password.
- homakov 9y agoThere are many differences, because your password used just once to create root hash. From root hash private key is generated, and no one is sharing password anymore