Hacker News Reader

Comment by abrowne | Hacker News Reader

If you want the Qt one, make sure to use KeyPassXC, the active fork of KeePassX.

I use keepassxc on MacOS, Windows, Linux, along with MiniKeePass on iOS. It's synced through my free Dropbox account. I just make sure to set the preferences so that every change to the key database results in a file save.

I daily use the exact same setup for all three, but with the Android equivalent.

...so it's not like this app is unheard of, per this thread's parent comment. Super odd that they didn't include it haha

> synced through my free Dropbox account

I was always a bit paranoid about this, even though I did it myself.

The decentralised alternative is to use something like SyncThing[0]. It's what I use and is only slightly more involved.

[0] https://syncthing.net

I use syncthing for some backups, no idea why I've never considered it for keepass. Probably cause I don't want to mix the two and clients don't offer it already integrated. Or are there any? It for sure wouldn't make building the project more easy, and the password manager is the one thing i still want to build form source to at least imagine I have full control over it.

What about Resilio Sync? They have a discount for one-time license. And it was formerly BitTorrent Sync. I'll have to check out Sync Thing.

Well, SyncThing is open source as well as being free.

I use keepassx and yeah it could use some tlc, but overall I consider stability a feature in security software. How does one tell if xc isn't just a bunch of wannabes making keepassx with blackjack and hookers until they break it? At least keepassx has taviso's off-handed Twitter comment that it "looks sane".

What I like about keypass is that it's not networked and not running in the browser, making the attack surface a lot smaller.

Keypassxc having such features(and apparently the old network protocol was vulnerable lol) is for me a strike against it.

Reply on news.ycombinator.com