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
Proton pass works just as well if not better for me. The autofill is much more reliable on Android than bitwarden was, although I did switch about a year ago.
You could use Synctrain or maybe Möbius Sync to SyncThing-sync a folder with your phone, then use Strongbox or KeePassium or any other KeePass-compatible app to work with the file?
But thousands of people have it working just fine. Not calling you out but it does work very well. Did you follow a step by step guide? I know websearch makes it hard to learn new tech things these days.
Just keep in mind, set up a default folder and file (filename.kdbx) to share on one device, add Remote Device (QR code helps there), go to Sharing Tab and select Default Folder. If the Default Folder isn’t ticked on both devices in the Sharing Tab on each, nothing happens. When you work it out, that folder can be called anything and you can get advanced with how or when it shares or which direction the data goes (think photo backup from mobile to desktop).
Convoluted, I know, but so is relying on a company to host for you in the cloud. They just hide all the complexity behind the interface. With Syncthing, once it’s set up between all your devices (and there is a way to quickly auto accept setup once further advanced/knowledgeable), it just chugs along in the background. Changes to keepass file appear almost instantly across each device once it’s opened.
Oh, I hope not. It’s not really that clear. I’ve been on it for a long, long time so would have got through that stage you tested with no issues. Having Basicsync now is nice, it’s just the webui on your phone with some quality of life improvements like when it turns on etc. Very simple and familiar across multiple devices.
Try comparing what I said with the official guide from “Configuring” downwards. Hits more than what I tried to communicate and has screenshots if you get lost.
When I first started with it, I just set it up on my phone with the Default Folder (and file inside) at /sync and then walked around to the other devices, open up Show ID on the new one I’m at, add remote from my phone and QR scan the new device. You then get a notification to accept the device, then make sure Default Folder in Sharing is ticked for both. You can just find devices on the network too.
The more devices, the greater redundancy on the keepass file if you lose a device or it fails. Sometimes there are conflicts with files that haven’t been synced properly (none of my family’s iOS devices sync always on in the background and I don’t use iOS so it’s not my problem and hasn’t been troubleshot) but you can merge conflicts in Syncthing in Keepass by merging both files together. Set up Simple File Versioning and 5-10 copies when you are confident with it. If you have a device that’s always on like a server, it tends to be the arbiter of truth and catches sync issues. Android/Linux/Windows just work for me.
I recall having issues and bouncing off of it on my first attempt, but I’ve been using it on GrapheneOS/Pixel 8 Pro without issue for at least 2 years now.
A little more than a year ago, Syncthing for Android had a lot of issues, there was a breaking change installed that required updates and the existing clients had issues, it has since been forked.
If you don’t need the granular security or family-friendliness it should provide.
Because the new CEO seems to really be wanting to find revenue and this step just reaffirms in my mind that he’s likely going to start reducing features for unpaid accounts.
That’s quite the disappointment. Probably need to prepare to switch away from bitwarden or at least research options for open source clients for my vaultwarden backend.
Before Bitwarden / Vaultwarden I went with Keepass (it was some fork don’t remember the exact name KeepassXC probably) synced via Nextcloud. It’s not as convenient as Bitwarden plus at least back then it didn’t support passkeys. So yeah, I don’t know what is actually out there. Honestly I don’t think it’s super urgent to start hunting for alternatives but probably we should have at least some ideas in case the Bitwarden team does some weird moves.
Someone can correct me, but this change seems to be targeting people who are repackaging bitwarden and selling it. It does feel like we are trending the wrong direction though.
If you read their announcement carefully you’ll find things like
All current features are available in both versions
Which strongly implies that the different versions will start to diverge over time. Then at one point they will just be like maah it’s not worth putting more work into the open source thing, we’ll focus on building new cool features yada yada yada. And this is how all the open to partly open to closed source rug pulls worked in the last years.
(If you want to do this the worst way possible like MinIO you also squash / delete the Git history the moment you announce you’re only working on closed source)
Yeah well, didn’t know this. I’m still running some old minio instances on my home server. Need to check if the docker images are still around otherwise I urgently need a backup plan…
Fucking hell, why didn’t they at least leave the old code available 😭
Well, a big reason I ended up with bitwarden is being able to have a family group that I can help foster, encourage, force my family to use a password manager by having/showing them how these work , why they should use them and continually point them to the app to save and/or retrieve passwords.
The barrier to entry for non technical users is much lower. I don’t want to manage making sure everyone’s db is safe/synced etc… either
I don’t know, my wife (0 technical knowledge) works perfectly, with daughter and personal databases. Of course, it’s true that I set everything up myself and I make sure the database is on the family NAS. I’m not judging you or anything, but while it’s true that setting it up is a bit more difficult, using it, in my opinion, is not at all.
I do run a number of self hosted things, (nextcloud, immich, plex). I had my own pw manager, and had tried keepass myself and when it came time to push the family to using a pw manager I just opted for bitwarden here vs taking ownership of managing that too!
Hell, it’s still a literal fight/push to make them understand the importance of it <sigh>
I’m using Strongbox on macOS and iOS. Uses a KeePass2 database in the background, does TOTP (so does KeePassXC), syncs via iCloud (but also supports SFTP, WebDAV, OneDrive, Google Drive, and Dropbox) and also keeps my Passkeys. And it supports Apple’s AutoFill API, so it works in basically any input field across the systems and feels “native”. No browser extensions (at least for Safari) needed.
And if it goes rogue, I can switch to e.g. KeePassium or any other KeePass-compatible app.
I might be a bit paranoid (or an idiot) but I think having the password and the totp in the same database (and app) somewhat negates the point of two-factor authentication.
It does negate the big issue of passwords leaking from the websites and that’s the most important part of even having totp.
Nobody is going to spend time to separate the 2 and maintain backups of two different things and all that extra effort when 90% of people don’t even use password managers.
I see 2FA as mostly a mitigation for users reusing passwords between services, which users of password mangers usually don’t. Of course, the password manger itself can be a single point of failure.
How? It’s not like the source code if no longer under GPL, it’s just that this specific compiled binary is under a different license but it doesn’t change anything for anyone in real life.
Also, why would users of a proprietary platforms (because Chrome is the proprietary version of free Chromium) care? FOSS people use different platforms, such as Helium browser, LineageOS, etc.
Same, probably going to switch to it eventually even though I don’t like having all my eggs in one basket. Proton provides me a good quality service, can’t lie.
I just cannot get on board with Proton Pass while I cant have a completely different set of credentials.
I keep my Proton passwords inside the password manager. Either I need to make my Proton password memorable and be my master password OR setup the 2 password mode where I need to remember and login 2 passwords.
They need some kind of privacy pass implementation to link your Proton pass to your Proton account while allowing completely separate credentials.
I keep the master password inside proton pass itself. I don’t want to be trusted with remembering anything. What if I lose my memory, ya know. They give a twelve word backup which you can use in case you get signed out of every device.
When Bitwarden got a meh “refresh” of the user interface and started vibe coding stuff (I’m not some super hard-line anti-AI person, but dammit, you absolutely should not vibe code security-critical apps), I switched to KeePassX. It was like coming back home! I used to use KeePass and KeePass 2, switched to Bitwarden for a long while, and while it was neat, KeePassX is just neater. (Doesn’t have cloud sync, but syncing the vault files with LocalSend is easy enough.)
Yup, I was supposed to say KeepassXC. (…I mean I probably considered using KeepassX at some point, it’s XC’s predecessor after all. But as I recall Keepass 2 worked well enough on Mono, so I didn’t need to switch.)
Also, whoopsies on XC’s AI use. At least they don’t seem to embrace it as much as Bitwarden, but still makes me go hmm.
This process is fully transparent and open for anyone to see, and it does not change with AI. We take no shortcuts. At KeePassXC, we use AI for two main purposes:
As an additional pair of “eyes” in code reviews.
In this function, AI summarises the changes (the least helpful part) and points out implementation errors a human reviewer may have missed. AI reviews don’t replace maintainer code review, nor do they relieve maintainers from their due diligence. AI code reviews complement our existing CI pipelines that perform unit tests, memory checks, and static code analysis (CodeQL). As such, they are a net benefit and make KeePassXC strictly safer. Some examples of AI reviews in action: example 1, example 2.
For creating pull requests that solve simple and focused issues, add boilerplate code and test cases.
Unfortunately, some people got the impression that KeePassXC was now being vibe coded. This is wrong. We do not vibe code, and no unreviewed AI code makes it into the code base. Full stop. We have used Copilot agent to draft pull requests, which are then subsequently tweaked in follow-up commits, and reviewed by a maintainer, openly for anyone to see, with the same scrutiny as any other submission. Good pull requests are merged (example), bad pull requests are rejected (example).
To be honest, I don’t really know where AI assistance stops and vibe coding starts. It was not my intention to say the KeepassXC team now only produces some half-assed unreviewed garbage.
I use KeepassXC myself, but OP has valid concerns about AI usage in security critical applications and I just wanted to point out that KeepassXC isn’t AI-free either.
If you are on Lemmy, theres very high probability that you also have the technical abilities required to self host Vaultwarden and stop relying on a greedy company for your most critical aspect.
I have Vaultwarden, it works with the web app and browser extensions. But is there a vaultwarden specific android app? I know technically I can use the Bitwarden app. But sometimes they update the Bitwarden app too fast for all the changes to translate into Vaultwarden and then im kinda forced to use the web app.
The web app is just a minor inconvenience to me so I continue to use it. Just wondering if there is an easier Vaultwarden specific solution for android.
Yes because using a different then normies app also means technical skills. In fact, haven’t your PhD diploma came along when you signed up for your Lemmy account?
I could but I don’t want. Self hosting something this important? I can’t login to any website without this software, including my email. It’s super critical.
Maybe that’s a bitwarden issue, I guess. One more point for selfhosting. Also, even if that were to happen to you, you most likely have it installed in more than one device. The chances of all sessions logging out at the same time would be extremely low.
Or just use and maintain Vaultwarden properly. All you need to do is set up watchtower along with vaultarden and you’ll always be up to date. I’ve never had this problem so yes, I will continue to store my credentials there :)
Yeah vaultwarden and photos are the 2 things i’m too nervous to selfhost. I do selfhost basically everything else but these 2 things are too important for me to mess up that I just don’t…
Bitwarden has much better enterprise options. KeePass is kind of dinky by comparison; even for a single user you immediately run into the problem “how do I sync my new password to my phone automatically?” Bitwarden was just an app that worked.
That being said ~ I see the writing on the wall, and will be going back to the dinky option. Again. This isn’t the first time I’ve been burnt, but I never seem to learn. Self-hosting seems to be the only sustainable long-term option after all. Hopefully the migration isn’t too painful.
I highly recommend anyone reading this get your export out while they still have a good export tool. First thing companies do in enshitification 101 is make it difficult to leave and trap you via inconvenience.
Because some people need non-technical people to share password solutions. Keepass is all or nothing for security and pass is ad administration headache for a family.
Lastpass limited the number of device types, phone OR desktop
I’d find it more likely they remove passkeys and TOTP from the free plan.
My fam will not like moving password managers again, but it might be time.
Need PC, Mac, Linux, Android, IOS, Passkeys, TOTP, Granular Permissions, keepass ain’t gonna cut it. Getting off my ass and making something isn’t impossible, but i’m not looking forward to figuring out passkeys, copy, paste and accessiblilty on IOS.
Lastpass limited the number of device types, phone OR desktop
The thing that shit me about LastPass doing that is that they used to do that. And I actually paid for it back when they did. Then they made it free for several years. And then they brought back the restriction, only at like 5x the price.
And in the meantime, quality of life of the service remained flat. I regularly had to go into the LastPass app and manually copy/paste because the autofill functionality didn’t work properly on Android. There was just no way it was a service of a quality that’s worth paying for. Bitwarden’s UX is incredible by comparison.
yeah talk about going out in a blaze of glory stupidity.
Fuck over the free users (features)
Fuck over the pay users (cost)
Fuck over the corporate users (over report the actual level of encryption, several vulnerabilities that exposed easy exfiltration, third party trackers running in zero-trust code)
Fuck over everyone, their DevOps dude running Tatuli on Plex got RCE’d and exposed their entire vault
It just blows my mind how so many comments use the term ‘purchase’ as if this new enshitification step still allowed for the dictionary meaning of the word.
I used to suggest bitwarden to everyone, now it’s basically ‘start using KeePass, keep a copy of your db in a USB drive in your safe, have fun’.
Yep, have been using KeyPass or KeyPassX for at least a decade now and just syncing across all machines (via syncthing). 100% reliable in my experience.
The fact that bitwarden raised 100 millions from venture capitalists for “acceleration” and small changes towards a closed license for premium features is a steady step towards enshittification.
The writing is on the wall and every announcement like that is a step further into enshittification to provide value for shareholders at the expense of thrle consumer base.
I still haven’t switched yet because life is going fast and I didn’t come around to do my backup file server yet, but I would suggest anyone reading this to look for an alternative because it will get worst.
I get the disappointment but you should still do it. In the short term, this announcement means nothing and the main risk is to 3rd party hosting/self-hosting. 1Password has had multiple breaches over the years.
“bitwarden apps will be the commercially licensed builds.” I don’t understand how this is going to change anything.
I self-host vaultwarden. I use the official Bitwarden app, it works swimmingly. Going the self-hosted route you get enterprise features (I don’t use em).
Doesn’t the licensing stuff connect with the backend not the app?
All current features are available in both versions
They will start making changes exclusively to the propriety app, and eventually the proprietary app will be completely incompatible with the FOSS app. They’re doing what Google did with AOSP.
Does this mean I will, or won’t be able to install the FOSS version through GitHub? Trying to stop repackagers from selling your project is one thing, but killing the source available installs would be another.
Open-Source is literally used as marketing tool for the under dogs until they reach a critical mass of users.
People were fighting on social media, defending the product, suggesting it, “it’s open source”, people were doing the marketing for them.
No wonder why people feel like they got raped, after all the hard work they have done for them…
But at least they didn’t contribute code, did you? Not me, because I am old enough to never use such products, it’s a classic rug pull, bait and switch.
Open source doesn’t mean it’s good, it must be hold by a bunch of strangers in T-shirt, not in full suite…
