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 everyone
If 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
I’m so tired of switching password managers… I currently use Vaultwarden with the official BW clients and I’ll switch if they actually go to shit.
Uh, what should I go with now? I don’t want to self-host password manager, as any downtime would be critical. Also, I heard handling sync in Keepass is a pain. Is there a reliable alternative, one that I don’t need to constantly worry about?
I’ve had a keepass file on my Nextcloud server for years and never had any sync problems whatsoever
Gotta love corporate announcements. “We’re making a change, but nothing will change. We also won’t tell you why we’re making this change.”
Pretty sure money is the reason. With a side dish of possible backdoor.
I was already using Vaultwarden for the server, just switched to Keyguard on Android and Desktop. Works perfectly.
There seems to be an open PR for a browser extension as well. Hope that’s merged soon.
From reading the thread, it looks like they are dodging the question of what features will be restricted to the commercial license versions (“case-by-case basis” apparently). They keep repeating “no change to people using the app currently”, “no change to self-hosting right now”, etc., but it doesn’t inspire confidence.
I would recommend to read the thread and ask questions there if you have any, but I would definitely have a backup plan ready.
The KeePass ecosystem is awesome and it’s what I use, it’s local-first and you can use Syncthing to have passwords across many devices. KeePassXC for desktop (+ browser extension if you need it), KeePassDX on Android (w/ Syncthing-fork), and if you use iOS, you have KeePassium and Strongbox (w/ Synctrain). The iOS apps are more limited, blame Apple for their restrictive ecosystem and high entry fee.
KeyGuard on Android can be a direct VaultWarden client.
Secrets is another decent KeePass client and works well with Gnome and other desktops that work well with libadwaita. It doesn’t have browser integration though, so it’s a non-starter for me.
How, if at all, does this change impact Vaultwarden?
VaultWarden is already it’s own thing code base wise, so, it likely won’t effect the hosted portion of it at all.
The apps though, sounds like right now, it sounds like it won’t make a difference, but, I think moving forwards it’d make sense to consider forking and making VW branded versions.
With that said, right now, the only reason you can choose your own domain is because BW allows you to self host their own product and VW just made their API respond the same way as BWs, so, as long as BW keeps allowing the self host option, I would imagine that there really isn’t much they can do about VW other than starting to play games with their API, which would also impact their paying customers.
deleted by creator
Scratch that, maybe don’t use Proton Pass. Just did some more searching, their CEO has donated millions of dollars to the Republican party. They also sponsored some alt-right French influencer (from my quick searching, a lot of racism, conspiracy, Holocaust denial, homophobia, transphobia, that sort). Yikes!
My bad for not looking more into this!
So they’re pulling a Mattermost?
This change has been coming for a while and I’m glad I started checking out KeepassXC. Will be moving over to that soon
redis, mongo, elastic, directus etc
Not sure why you’re getting dv’d but you’re right. Redis, Mongo, ElasticSearch all did this too. Latest offender was minio
Made the move some time back, just as Im wishing move as much as possible fully offline for a number of reasons. KeepassXC and DX are fantastic
I’m on Vaultwarden but using Bit warden’s clients. I hope these continue to be open source, they’re pretty good IMHO.
Try KeyGuard as a VaultWarden client on Android.
Good zu know, thanks!
Keyguard is not FOSS, just fyi.
Agree but if BW go completely rogue, it’s an option to use with VaultWarden and continue on, for now.
