Concerns Raised over Bitwarden Moving Further Away from Open-Source
Bitwarden faces criticism for moving away from open-source principles due to a new SDK dependency with restrictive licensing. The founder clarified the SDK and client are separate, but community concerns persist.
Read original articleConcerns have emerged regarding Bitwarden's shift away from open-source principles, particularly following a recent pull request that introduced a new SDK dependency for the desktop client. This SDK includes a clause that restricts its use to Bitwarden applications only, raising questions about the software's classification as free software. Users have expressed their worries on GitHub, highlighting that the SDK's licensing terms may prevent the development of compatible applications. Bitwarden's founder and CTO, Kyle Spearrin, responded to these concerns, clarifying that the SDK and the client are separate programs and that the issue is a bug that they plan to resolve. However, the GitHub ticket discussing these issues has since been locked to collaborators only, leaving the community uncertain about the future of Bitwarden's open-source status.
- Bitwarden is facing criticism for moving away from open-source practices.
- A new SDK dependency has raised concerns about licensing restrictions.
- The founder of Bitwarden has addressed the community's concerns, stating the SDK and client are separate.
- The GitHub discussion on the issue has been limited to collaborators, causing further uncertainty.
Related
Bitwarden (the SDK and mobile app) is not FOSS
Bitwarden password manager faces licensing challenges due to its non-FOSS SDK, limiting its availability on platforms like F-Droid. Community forums discuss implications and hurdles for FOSS compatibility.
Let's not celebrate CrowdStrike – let's point to a better way
The Free Software Foundation criticizes the CrowdStrike incident, advocating for decentralized free software to reduce reliance on proprietary providers, emphasizing informed consent for updates and better collaboration among developers.
Ask HN: Concern over Chinese Software?
Concerns about Chinese software are rising due to U.S.-China tensions, CCP influence, and privacy issues. The author highlights challenges in avoiding Chinese products and seeks strategies to mitigate risks.
Can we trust Microsoft with Open Source?
Microsoft is experiencing internal conflict over its commitment to open source, particularly with the .NET platform, following the restriction of the "Hot Reload" feature to proprietary products, prompting community backlash.
Please Stop Inventing New Software Licences
Terence Eden critiques the Cyph app's proprietary license, which complicates community contributions and collaboration due to ambiguous terms. He urges developers to prioritize clarity in open-source licensing.
This is understandable, the password manager market is saturated and implementing new features like Passkeys is far from trivial.
Still, they are the only real option for a one-click mostly open source password manager that works across all the major platforms and that supports modern features.
Bitwarden is no longer free software - https://news.ycombinator.com/item?id=41893994 - Oct 2024 (71 comments)
I’m a customer of both services. I started with 1Password since its early days and have been using the family plan for the past 5+ years.
I used BitWarden when starting with Teams, as it is cheaper and presumably scalable. I hope that if things grow up, we can either host it ourselves or the pricing is affordable enough.
If Bitwarden becomes as “successful” as 1Password, people/companies will actually just use 1Password.
I think, now, the idea would be to start moving all critical ones to Keepass; and use a better UX client on top of the database.
Bitwarden is no longer free software
https://news.ycombinator.com/item?id=41893994
BitWarden leaves open source community https://news.ycombinator.com/item?id=41896750
> 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.
Tempest in a teapot.
What about reporting a bug and chill? Instead of immediately jumping the gun and flooding the issue tracker of the one company that still tries with preaching? What is this going to achieve? Of course they locked it. Shame on everyone who commented some RMS-inspired lament into their issue queue.
I will continue to vote with my wallet, with other open-first solutions like ente and etesync.
Part of why I do this is so that if the company changes direction, the community can potentially fill in.
With the momentum behind vaultgarden, maybe open clients will flourish too.
That's a big deal to some, no doubt, but it's important to be precise about language in cases like this, especially since folks will undoubtedly assume that this means secret user-hostile things will now be embedded in the source code, sight-unseen.
Related
Bitwarden (the SDK and mobile app) is not FOSS
Bitwarden password manager faces licensing challenges due to its non-FOSS SDK, limiting its availability on platforms like F-Droid. Community forums discuss implications and hurdles for FOSS compatibility.
Let's not celebrate CrowdStrike – let's point to a better way
The Free Software Foundation criticizes the CrowdStrike incident, advocating for decentralized free software to reduce reliance on proprietary providers, emphasizing informed consent for updates and better collaboration among developers.
Ask HN: Concern over Chinese Software?
Concerns about Chinese software are rising due to U.S.-China tensions, CCP influence, and privacy issues. The author highlights challenges in avoiding Chinese products and seeks strategies to mitigate risks.
Can we trust Microsoft with Open Source?
Microsoft is experiencing internal conflict over its commitment to open source, particularly with the .NET platform, following the restriction of the "Hot Reload" feature to proprietary products, prompting community backlash.
Please Stop Inventing New Software Licences
Terence Eden critiques the Cyph app's proprietary license, which complicates community contributions and collaboration due to ambiguous terms. He urges developers to prioritize clarity in open-source licensing.