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:

You may not use this SDK to develop applications for use with software other than Bitwarden (including non-compatible implementations of Bitwarden) or to develop another SDK.

This violates freedom 0.

It is not possible to build desktop-v2024.10.0 (or, likely, current master) without removing this dependency.

  • Andrew@piefed.social
    link
    fedilink
    English
    arrow-up
    127
    arrow-down
    1
    ·
    edit-2
    1 month ago

    There’s a lot of drama in that Issue, and then, at the very end:

    Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.

    the SDK and the client are two separate programs
    code for each program is in separate repositories
    the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

    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.

      • superkret@feddit.org
        link
        fedilink
        arrow-up
        114
        arrow-down
        1
        ·
        1 month ago

        They claim the SDK and Bitwarden are completely separate, so Bitwarden is still open source.

        The fact that the current version of Bitwarden doesn’t work at all without the SDK is just a bug, which will be fixed Soon™

        • umbrella@lemmy.ml
          link
          fedilink
          arrow-up
          14
          ·
          1 month ago

          further translating it: they are closing it down but trying to make it look like they arent

      • TheOubliette@lemmy.ml
        link
        fedilink
        arrow-up
        43
        arrow-down
        1
        ·
        1 month ago

        They’re trying to argue legal technicalities because acknowledging that they’re trying to reduce compatibility with servers like vaultwarden would be bad PR.

        Per their new license, anyone that uses their SDK to build a client cannot say, “this is for Bitwarden and compatible servers like vaultwarden”. They cannot support those other servers, per their license. Anyone that gets suckered into using their SDK now becomes a force against alternative implementations.

    • unbroken2030@lemmy.world
      link
      fedilink
      arrow-up
      13
      arrow-down
      13
      ·
      1 month ago

      There is always a very vocal minority itching to cause as much drama as possible. It’s very discouraging to see in general. I agree with and want more FOSS, but I’m not sure I’d ever consider making it myself; it’s not worth extra stress personally.