Hacker News Reader

Comment by Pooge | Hacker News Reader

KeePassXC is the way to go. Install F-Droid on your Android smartphone, get KeePassDX. This way, you have a desktop and Android client.

I'd recommend setting a very strong password, with a key (you can generate one when you create the database) and a long decryption time.

If you need help setting strong passwords, I recommend EFF Dice-Generated Passphrases[1].

[1]: https://www.eff.org/dice

View on HN

Do you have any recommendations on syncing the database file between devices?

I do it manually every now and then. As for an automatic approach, you could try KeeShare[1] or Syncthing[2].

[1]: https://keepassxc.org/docs/KeePassXC_UserGuide.html#_databas...

[2]: https://syncthing.net/

I just keep my KeePass database synced in $generic_cloud_storage. Since the database is encrypted and decrypted on the client side using a password and a key file, and I'm not keeping the key file synced (I copy it manually to my devices), I haven't found it to be an issue to keep the database in cloud storage even though I obviously wouldn't trust the provider with my cleartext passwords.

^^ Just to emphasize:

USE A KEY FILE in addition to a password.

Your paranoid self can sleep well at night (as long as your key file is not being synced).

Basically any file sync client. Just keep the keepass database in the folder that gets autosync'd and sync the folder to each device you need keepass on

Keepasswandroid can integrate with any cloud storage and will perform merge when needed

I've been happily using syncthing for 2 years now. Syncs my password files between 3 computers and 2 phones.

There's manual syncing, and automatic syncing.

Manual: All clients I've seen have the capability to merge databases. So you have one copy of the database in whatever online file storage service, plus each device will have its own local copy. Pull down the online db, do a bidirectional sync between the two databases, push back online.

Automatic: some clients natively support webdav, dropbox, etc as the master copy of the db file and will transparently do the change syncing for you.

This guy suggest SyncThing for automated route of syncing databases of password savers.

https://www.ctrl.blog/entry/keepass-vs-bitwarden-server.html

https://syncthing.net/

Syncthing! Has Windows/Linux/Android/iOS clients. Works perfectly.

I had so many issues with this, it feels like you have to keep track of whret you do changes and when it has synced it. Otherwise it won't merge and you will have to do it manually.

Bitwarden is so much easier sadly.

Honestly, I think I had syncing conflicts maybe once or twice, and even then the merge feature worked without any hiccup.

Maybe it does help the fact that I have my NAS always online, and I treat my mobile devices mostly as "read-only" - i.e, if I have to create a new password it will almost surely be on my desktop / laptop.

Keepass2Android and KeePass2 official syncs reasonably well. Or the XC implementation if you prefer

I use rsync on termux and zerotier for remote access. Mounting sshfs on android is also great if you don't need any passwords when offline.

I keep my password database in a Google Drive directory. Clients exist on Windows, Mac, Android, IOS.

Keepass2Android can sync and merge from a variety of file sync services.

Self-hosted Nextcloud supports WebDAV. It's been working great for me.

We have the family password database in Google Drive. It works suprisingly well, and it haves file versioning.

I'm currently using KeePassDroid on my smartphone, in case you also tried it could you tell me why you prefer KeePassDX? I've never heard of it before

Reply on news.ycombinator.com