- cross-posted to:
- bitwarden@lemmy.ml
- linux@programming.dev
- cross-posted to:
- bitwarden@lemmy.ml
- linux@programming.dev
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?
This plus the syncthing announcement about the Android client ending support is a bad day indeed. I was just thinking about self hosting instead of KeePass + SyncThing now it’s back to the drawing board once it stops working 😵💫
The syncthing fork on f-droid is still an option. An issue has been opened on the github repo. Lets see what will happen with the fork
I do have it installed through F-Droid. I thought I read that they weren’t really going to be focusing on it at all, so updates may just die out.
Brings the little hope that my current situation won’t die!
I don’t know enough about Java directly to contribute anything useful, sadly.
I am talking about the fork. It is operated by someone else.
I literally just saw that as well, not really too sure what to do now lol.
Vaultwarden?
Keepass2Android supports many cloud options including Nextcloud and OwnCloud so it sync with storage directly. At least with Dropbox it works like a charm.
The whole point of self-hosting it is to not put the information on a public cloud. But, thankfully the F-Droid fork is still going on and I had misread it anyway.