-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Desktop version 2024.10.0 is no longer free software #11611
Comments
Thank you for reporting this issue! We've added this to our internal tracking system. |
Namely trying to build with
|
Also see bitwarden/sdk-sm#898. It looks like this is part of a deliberate campaign by Bitwarden, Inc. to fully transition Bitwarden to proprietary software, despite consistently advertising it as open source, without informing customers about this change. For whatever the opinion of one user is worth, I've switched away from Bitwarden due to this. |
I noticed and reported a similar problem with the NPM releases of the CLI client (#10648) two months ago, and I have yet to receive a response. Bitwarden definitely seems to be moving away from being open-source software without making any sort of announcement about it. |
what alternatives do you guys recommend? |
Bitwarden was good to me.. Now it's time to switch to alternatives... |
Best alternative is to fork the version before this change! |
Ohhh noooo... That's a shame. You're right: i'll go to a fork or to any alternative! |
I would be careful going to "any alternative". It's your passwords you're talking about. Also, a fork of the client still leaves the open issue of relying on the server service or software. |
This is... concerning to say the least. I'm a long term paid Bitwarden user, and it's making me reconsider that decision. |
I'll be looking for an alternative after hearing this. Quietly moving away from open source raises serious concerns. |
well so it can be striped from us at any time? |
That's interesting for a server, and while the server has a web client, are there comparable open source clients too for desktop and/or mobile? |
If it's for the home Vaultwarden. |
No no no, not Bitwarden please. A service i dearly loved and was satisfied with :( |
Why home use only ? |
enshitification is inevitable with these god forsaken companies |
Note that the SDK is used (and enabled as a feature flag) not only in the release of desktop app, but also in the browser, CLI and web clients. This mean that all versions of BitWarden 2024.10.0 are using the SDK. |
How many times do we have to teach companies that try to rug pull this lesson, you want to end up like redis? This is how you end up like redis. |
Yikes, that sucks |
It's practically a given with almost any VC (venture capital) or PE (private equity) backed company with worth between 10 million and 1 trillion USD. When outside of this range, they can do what they want. People keep getting surprised every time this happens, but it's so common as to be inevitable indeed. |
Bitwarden has before released projects advertised as "open source" while not under a non-open restrictive license details, discussion. This may now indicate a pattern or direction. |
This sucks. I am going to develop an alternative desktop app which wraps Vaultwarden's web interface using Tauri, if anyone is interested. |
So I guess all my customers and myself of course will be moving to an alternative. |
Removed the annual subscription (never used the extra features, I had it only to support the project) and moving away very soon to a truly free software solution. Very disappointed since I have pushed a lot of people toward Bitwarden. |
Same to me. And I quite regret it now... |
Spirit of open source died long time ago. Open source is now a business model. |
Hi @brjsp,
Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug. |
According to me, the spirit of open source still lives in free software philosophy. |
@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. |
Pull request #10974 introduces the
@bitwarden/sdk-internal
dependency which is needed to build the desktop client. The dependency contains a licence statement which contains the following clause:This violates freedom 0.
It is not possible to build desktop-v2024.10.0 (or, likely, current master) without removing this dependency.
The text was updated successfully, but these errors were encountered: