cross-posted from: thelemmy.club/post/57178796
cross-posted from: thelemmy.club/post/57178743
RyanL Bitwarden Employee
Hello everyone!
Starting in the next release, the Bitwarden apps published to the various stores will be the commercially licensed builds. No action is needed, and the apps will work exactly as they do today.
Bitwarden remains committed to open source security and transparency The GPLv3 OSS licensed version continues to be updated and published on GitHub All current features are available in both versions License details are on GitHub Bitwarden remains committed to a robust, free forever plan for everyoneIf you have any questions, please ask them in this thread. Thanks all!
EDIT:
Bitwarden is not going closed-source You can still fork Bitwarden No change to self-hosting, the licensing change affects those who are repackaging and reselling Bitwarden The free plan is here to stay permanently
Mustachius_Grumpius@thelemmy.club
peyotecosmico@programming.dev
Estebiu@lemmy.dbzer0.com
Dirk@lemmy.ml
PrinzKasper@feddit.org
AustralianSimon@lemmy.world
Zachariah@lemmy.world
Well, we all know how this ends…
It’s a really sad day for me, I love Bitwarden, it’s easily the best password manager I’ve used, and I’m in IT, I’ve used a bunch.
Fuck private equity, fuck it to death. But until then, I’ll be moving my test setup for KeyPassXC into production over the coming weeks and months.
I was happily subscribed to Bitwarden for years for my personal account, I moved several people and a whole company onto it’s platform. We had a good run, time to move on.
nibbler@discuss.tchncs.de 2 weeks ago
why not vaultwarden?
If I’m going to have to host my own infrastructure, I don’t want it tied to Bitwarden, given the new direction of the company.
I fully support Vaultwarden though, and I wish them well.
I’ll be going with KeyPassXC and Syncthing.
lemmyvore@feddit.nl 2 weeks ago
Vaultwarden (and all the client apps) depend on Bitwarden for the API spec. If Bitwarden introduces closed features in the API that Vaultwarden can’t/won’t implement, but the client apps do, it will split the spec. They can also introduce API license keys, which would render Vaultwarden mostly irrelevant.
The only way for Vaultwarden to remain relevant going forward is to own it and split ways from Bitwarden. This would in turn mean that the FOSS client apps have to decide which to support. But I think the ecosystem is going to fragment eventually anyway, so the sooner every app decides which way they want to go, the better.
altphoto@lemmy.today 2 weeks ago
I’m. Using Vaultgarden but its not clear if the Android app will still be available.
1984@lemmy.today 2 weeks ago
100% but move where? I’m not going to self host something this critical.
sonstwas@sh.itjust.works 2 weeks ago
You can use KeePass on mobile, look for KeePassDX on fdroid.