3 ms·
This reminds me of something I want: a centralized password manager where * The entire file is encrypted, * Using OPAQUE, * On a FOSS local native client *
by gavinhoward 4y ago
This reminds me of something I want: a centralized password manager where
* The entire file is encrypted,
* Using OPAQUE,
* On a FOSS local native client
* That integrates with a FOSS browser extension that pulls the information only from the local copy.
* And the only thing the server does is store the file and user account information.
How hard could it be? (Well, outside of getting the cryptography right.)
Looking at this incident and the behavior of LastPass, it seems it's impossible. Or it's too inconvenient for users.
- c0balt 4y agoWell, the stopgap solution for this scenario is quite simple: Keepassxc + Keepassxc Browser Extension + Cloud Storage of your choice. OPAQUE is not covered but I'd argue that that would puttoo much of a restraint on the storage layer. Both Keepassxc[0] and the browser extension are FOSS and the cloud storage may be FOSS, like Nextcloud or "just" whatever works for you rn (Google Drive, Seafile, ...). On android Keepassdx[2] (with autofill) can help too. The only major pitfalls of this model is cross-device sync, i.e., you edit the file on device A while saving a change on B etc. Though this isn't really a problem if you (a) are using it alone or (b) make sure you keep backups. In case they do conflict it can merge multiple versions. [1]: https://keepassxc.org/ https://keepassxc.org/ [2]: https://www.keepassdx.com/ https://www.keepassdx.com/
- gavinhoward 4y agoYes. I use KeePassXC in exactly this way.