←back to thread

238 points ferbivore | 1 comments | | HN request time: 0.323s | source
Show context
andag ◴[] No.41894416[source]
Going proprietary is one thing, but doing it in several steps in different repos and saying nothing about it I really don't like...

What are open alternatives at this point?

replies(2): >>41894525 #>>41895554 #
ferbivore ◴[] No.41894525[source]
The KeePass ecosystem has gotten a little bit better. It's still not exactly seamless. File sync across all of Windows, Linux, macOS, iOS and Android seems to involve either proprietary user-hostile sync tools or dealing with lots of jank.

As far as I can tell, the only competitor with a similar feature set that even claims to be open-source is Proton Pass. But I can't find any information on whether the server side can be self-hosted.

replies(2): >>41894633 #>>41895372 #
1. selfhoster11 ◴[] No.41894633[source]
KeePass as an ecosystem (and possibly other file-based ecosystems) is something I’ve used for around a decade, and while it’s not perfect, I am 100% sure it will be there for me in another decade. I want to own my passwords, and KeePass feels like a safe pair of hands that won’t turn hostile when I’m not looking.

IMO, the secret to keeping the passwords synced with KeePass, is to make sure your client has a direct feature to sync the passwords database to a remote server - SFTP, DAV, SMB, etc. Then all you need to do is to set up a single remote file share to serve that file. Or sync manually, assuming your passwords change slowly - KeePass 2 can sync changes automatically between KDBX files.