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.

    • superkret@feddit.org
      link
      fedilink
      arrow-up
      113
      arrow-down
      1
      ·
      17 days 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
        ·
        17 days 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
      ·
      17 days 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.