Desktop version 2024.10.0 is no longer free software · Issue #11611 · bitwarden/clients
github.com
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: Y...

@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.

  • blackfire@lemmy.world
    611·
    22 days ago

    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.

  • 7ai@sh.itjust.works
    4819·
    22 days ago

    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.

    • Lojcs@lemm.ee
      415·
      22 days ago

      They literally said the issue was an unintentional bug and then fixed it. How is that damage control?

      • Atemu@lemmy.mlOP
        2·
        20 days ago

        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.

      • Corgana@startrek.website
        22·
        21 days ago

        Did you know that Mozilla is literally worse than Google and Meta? It’s true! Line 4,362 of the old “Firefox Send” source code contains a unicode character that in a very specific part of papua new guinea is used as a mark of shame against trans people. Also I am not paid by Google!

    • MoonlightFox@lemmy.world
      2·
      21 days ago

      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.

      • ᗪᗩᗰᑎ@lemmy.ml
        3·
        21 days ago

        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.

      • JustMarkov@lemmy.mlEnglish
        2·
        21 days ago

        Yes, it does works well, but has its caveats. You have to set up your own sync, either using a Syncthing or any other 3rd party app as KeePassXC does not have any sync option built in. KeePassDX has a good article about syncing a database.

      • LukácsFan1917@lemmy.mlEnglish
        1·
        19 days ago

        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

  • lemmeBe@sh.itjust.works
    11·
    22 days ago

    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.

    • JustMarkov@lemmy.mlEnglish
      9·
      22 days ago

      I’ve switched to KeePassXC on pc + KeePassDX on mobile after that whole drama. Proton Pass is also interesting, but there’s no way I’m gonna use cloud-based password managers anymore.