Bitwarden introduced a non-free dependency to their clients. The Bitwarden CTO tried to frame this as a bug but his explanation does not really make it any less concerning.
Perhaps it is time for alternative Bitwarden-compatible clients. An open source client that’s not based on Electron would be nice. Or move to something else entirely? Are there any other client-server open source password managers?
The downside to Keepass is it is not self hosted, as in it’s designed to run locally per device. Yes, you can put the database file on a network and have multiple clients from different operating systems access the database, but you will end up with collisions and database issues. Ask me how I know.
Running cross platform Keepass (and it’s various forks) is absolutely doable, but it is not as seemless as BitWarden. I’m running self hosted VaultWarden and I’m hoping to run it for a long time as it’s much easier than Keepass.
Yes, that’s a fair point
For what it’s worth, I only ever had sync issues when sharing a database between devices with transient connectivity. Once I added an always-on instance of Syncthing into the mix, collisions were a thing of the past.
We’ve been using KeePass trouble-free for many years now, sharing a single database across more than 6 devices, with frequent use and modification.
Syncthing just announced they won’t develop their Android app anymore. 🫤
Noooo! Ugh, that’s so disheartening to hear but I can’t fault imsodin for his reasons. I sincerely hope that someone steps up to the plate, even if only for the F-Droid releases.
For anyone else interested, the discussion is taking place here:
https://forum.syncthing.net/t/discontinuing-syncthing-android/23002/7
Ah shit, I hadn’t heard that. Another one bites the dust because of Google’s Play Store insanity. Maybe SyncThing-Fork will continue? 🤞
Source: https://forum.syncthing.net/t/discontinuing-syncthing-android/23002
Edit: Aaand like 10 posts down in my feed https://lemmy.world/post/21070831 lol 😭
While the official syncthing-android is no longer being updated, syncthing-fork is still going strong
KeePassXC here, ÷1 for the exact same issue with the exact same solution (ST with an always-on “server”) 👍
Eh, I have used KeepassXC over multiple machines using NextCloud to sync it for years now and have never had any conflict.
This. I have been running it the same way for some time now. Even if you change something on one machine and something else on another nextcloud will just happily inform you of the conflict and then you can open both databases and cherry pick. Never had corruption issues.