Open source tool chooses to become more open than ever

Bitwarden isn’t going proprietary after all. The company has changed its license terms once again – but this time, it has switched the license of its software development kit from its own homegrown one to version three of the GPL instead.

The move comes just weeks after we reported that it wasn’t strictly FOSS any more. At the time, the company claimed that this was just a mistake in how it packaged up its software, saying on Twitter:

It seems like a packaging bug was misunderstood as something more, and the team plans to resolve it. Bitwarden remains committed to the open source licensing model in place for years, along with retaining a fully featured free version for individual users.

Now it’s followed through on this. A GitHub commit entitled “Improve licensing language” changes the licensing on the company’s SDK from its own license to the unmodified GPL3.

Previously, if you removed the internal SDK, it was no longer possible to build the publicly available source code without errors. Now the publicly available SDK is GPL3 and you can get and build the whole thing.

  • schizo@forum.uncomfortable.businessEnglish
    267·
    2 days ago

    Wow, a commercial open source product that COULD have pulled a rugpull, looked for all the world like they were planning a rugpull, just uh, did the right thing?

    Good job, Bitwarden.

    • gsfraley@lemmy.worldEnglish
      68·
      2 days ago

      I know, it’s a huge relief seeing this as someone who uses the free tier. I think I’ll cough up for the advanced tier if they stick to their guns on this decision.

    • njordomir@lemmy.worldEnglish
      14·
      2 days ago

      I will remember this, even more so because of the confused drama that preceded it. In general, I find it difficult for me to endorse any commercial entity, but Bitwarden has my admiration and I will continue to offer it as a better alternative to people I see storing their passwords in Chrome or Lastpass. I’m also happy to pay a bit to support a good product and will continue to support the development even if I switch to self-hosted at some point.

  • BassTurd@lemmy.worldEnglish
    44·
    2 days ago

    I’m so glad this happened. I really wanted to believe them when they said it was an error and would corrected. It appears that in relatively short order they addressed the issue, gave an explanation, an expectation, then nailed it. I hate when I recommend something, then have to backtrack because they changed.

  • radamant@lemmy.worldEnglish
    61·
    1 day ago

    I think I’m still switching to keepassxc, but I’ll still recommend bitwarden to normal people (and my bitwarden account is paid til 2027 anyway, lol)

    • NuXCOM_90Percent@lemmy.zipEnglish
      2·
      19 hours ago

      Keepassxc is great if you don’t need to synchronize passwords across too many locations and do not require anything where state matters (mostly related to stuff like yubikeys). It DOES have the vulnerability in that a bad actor has infinite time to crack it should they get a hold of the file whereas bitwarden still lives on a server.

      But they are very different products with very different capabilities. Whether someone needs bitwarden over keepass is going to be a question of use cases.

  • penquin@lemm.eeEnglish
    1759·
    2 days ago

    Call me cynical, but I don’t think it was a “packaging bug”. I think they felt the backlash from their users. I mean, it’s still great and now I’ll go back to using their app.

      • penquin@lemm.eeEnglish
        11·
        7 hours ago

        Cry me a river. Fucking internet weebs, one can’t even express their opinion without everyone whining about it. Lmao.

        • Abnorc@lemm.eeEnglish
          1·
          4 hours ago

          You can express your opinion, but other people can criticize it. It’s just how these sites work.

        • frayedpickles@lemmy.cafeEnglish
          12·
          6 hours ago

          You literally asked us to call you cynical, dumdum. Why are you asking for something and then getting butthurt when it’s provided? That’s what toddlers do.

    • Bezier@suppo.fiEnglish
      6·
      1 day ago

      I expected the same by default, but after learning more I find it unlikely. They had a pretty good explanation for it being a mistake.

    • BearOfaTime@lemm.eeEnglish
      35·
      2 days ago

      There was a really good explanation by a rando about how it happened. Seems a dev made a mistake when publishing a change.

      Apparently bitwarden immediately changed internal procedure for publishing changes.