4 ms·
I have successfully used this for some time, but migrated away to just pass because synchronizing a pass "db" with syncthing tends to work much better.
by darthrupert 2y ago
I have successfully used this for some time, but migrated away to just pass because synchronizing a pass "db" with syncthing tends to work much better.
- zikduruqe 2y agoPass, then syncing to a bare git repo inside your own network is the simplest way to go.
- darthrupert 2y agoGood point, using git with this would probably make more sense.
- teekert 2y agoI switched away from KeePassXC because I kept having sync issues with the DB :). Could have something to do with the way I work (always several PC on/active and my own NextCloud install with issues from time to time...). Vaultwarden never had any sync issues. I guess because changing one login will give you 2 versions of the entire database when a conflict occurs, for Vaultwarden, it's just that one credential, which hardly ever happens.
- mbirth 2y agoKeepassXC can sync changes between your opened database and the (modified) file on your storage. However, you need to make sure your sync tool doesn’t see conflicts and renames the file, i.e. don’t save the database on multiple systems at nearly the same time.
- teekert 2y agoOh that is nice, but NextCloud never made effective use of that. It's been a while but I also found the browser plugins and methods to use the DB on mobile platforms cumbersome. Idk, perhaps much has changed, I have been on Vaultwarden for years now, and more recently switched to Proton Pass. Both have excellent Web UIs, iOS/Android apps and browser plugins. Moreover, Vaultwarden and Proton Pass make using Passkeys and sharing credentials with org or family members trivial (arguably Proton Pass even more so than Vaultwarden).