@brjsp thanks again for submitting the concern here. We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.
The original sdk repository will be renamed to sdk-secrets, and retains its existing Bitwarden SDK License structure for our Secrets Manager business products. The sdk-secrets repository and packages will no longer be referenced from the client apps, since that code is not used there.
This appears at least okay on the surface. The clients’ dependency on sdk-internal didn’t change but that’s okay now because they have licensed sdk-internal as GPL.
The sdk-secret will remain proprietary but that’s a separate product (Secrets Manager) and will apparently not be used in the regular clients. Who knows for how long though because, if you read carefully, they didn’t promise that it will not be used in the future.
The fact that they had ever intended to make parts of the client proprietary without telling anyone and attempted to subvert the GPL while doing so still remains utterly unacceptable. They didn’t even attempt to apologise for that.
Bitwarden has now landed itself in the category of software that I would rather move away from and cannot wholeheartedly recommend anymore. That’s pretty sad.
This makes sense and is quite common for opensource businesses. They have the main product which is open then they have a business only element either a module or plugin part which is designed for businesses not gen pop and isnt open. They screwed up the delivery on here and badly communicated it but if they did it right nobody would have noticed the secrets managment part at all because they don’t use bw business.
The way the founder replied coldly and closed the GitHub issue is pretty telling. Now they’re doing damage control.
It’s usually better to stay away from VC funded software. They exist for the sole purpose of turning a rich guy’s million dollars into 100.
They literally said the issue was an unintentional bug and then fixed it. How is that damage control?
They were doing the same on other repos for months.
Both their npm module and android client.
On android they tried to get people to add their own fdroid repo because the official fdroid has not had updates for 3 months due to the license changes.Edit: Looking at it now compared to 4 days ago, they apparently got frdoid to remove bitwarden entirely from the repo. To me this looks like they are sweeping it under the rug, hiding the change pretending it has always been on their own repo they control.
Next time they try this the mobile app won’t run into issues, the exact issues that this time raised awareness and caused the outcry on the desktop app, which similarly is present in repos with license requirements.
If they were giving up on their plan, wouldn’t they “fix” the android license issue and resume updating fdroid, instead of burning all bridges and dropping it from the repo entirely, still pushing their own ustom repo? Where is the npm license revert?
Thanks for the input and research.
One does not “accidentally” build a proprietary SDK for months and make the clients depend on it, intentionally violating the GPL.
They even publicly admitted to doing precisely that, defending their GPL violation with dubious claims how the GPL supposedly works.
deleted by creator
Does it work well from a user experience standpoint? I am considering switching from my current provider to KeePass XC. Usability is important, I also need to share some passwords with my SO. She is good with technology and computers, but not a dev.
Check out Proton Pass. I migrated my Bitwarden to it and its not just fast compared to Bitwarden but the UX is really nice. That said, I’m still sticking with Bitwarden, but will happily move away and give my money to Proton if they ever actually stop making their client open source.
deleted by creator
It absolutely rules for all kinds of info you don’t want laying around loose on a device. The sync issues others have mentioned are just a result of it giving you more control over file management. I don’t even sync I just use an SD card
Too bad because there are no other Bitwarden cons for me. Any recommendations?
Tried Proton Pass yesterday, and while it looks nice, browser extension not having a password lock is a deal breaker for me.
Also, I found out in the evening that after trying out Pass during the day and quitting on it, all my aliases in the SimpleLogin are gone. I know Proton owns it, but I wasn’t expecting that by deleting data on Proton (not the account itself), aliases could get deleted…
Still, not sure if it’s connected. I use SimpleLogin independently of other Proton services, but same primary email. Waiting for support.
deleted by creator
Keepass2Android Offline also works very well. It has a somewhat different feature set compared to DX.
I found it to be more stable at remaining permanentl unlocked, and DX dropped the 3rd domain level for password matching on either websites or apps, I don’t remember.
On the other hand DX works better for adding new credentials or making changes. Since I usually do that on desktop it doesn’t matter much for me.deleted by creator
The offline version is on izzyondroid.
The design is worse, yes.I don’t think it matters much because most of the time you only see the autofill thing, not the app.
When you do go to the app, it is to select between multiple credentials, which is still a split second action.On mobile I have my 2fa in a different more convenient app (aegis), though k2a does allow to copy 2fa codes
Thanks for the info. How does it sync?
Never mind. Now I see it’s with SyncThing.
It doesn’t.
Both DX and K2A-O open a local keepass file.
They are capable of reloading the file when it is changed, and can be set to immediately write out changes to the file.
Then you take whichever file sync tool you like and sync it with all other devices using it. As long as the sync tool can sync files in your internal storage, it will work.I use syncthing, with a dedicated keepass folder containing only the database file. Then I simply add all my devices to the share and it’ll sync any changes to all other devices. I also have version history enabled for the share.
Nice. Thanks for details! 🍻
I’ll try it out over the weekend.
Sorted. Had a bit of trouble debugging issue with Librewolf and the extension, but got it working.
While I was at it, converted my notes from Anytype to Joplin, and set up sync as well. Wanted to try out Joplin for quite some time now.
Weekend started nicely. ☕
