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

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.

  • rozlav@lemmy.blahaj.zone
    0·
    1 month ago

    Nobody here talks about keepassxc ? I’ve been using it for almost a decade, it can be used with sync tools to be shared, I’ve managed to have db keepass file opened on several computers and it did work well. Gplv3 here https://keepassxc.org/

    • EveryMuffinIsNowEncrypted@lemmy.blahaj.zoneEnglish
      0·
      1 month ago

      I just switched over. Honestly, I like it even more than Bitwarden. Then again, I don’t sync my stuff between devices because I’m old I guess. Lol. It makes it easier to switch because I don’t have to deal with stuff like Syncthing.

    • Atemu@lemmy.ml
      0·
      1 month ago

      Keepass isn’t really in the same category of product as Bitwarden. The interesting part of bitwarden is that it’s ran as a service.

    • unrushed233@lemmings.world
      0·
      1 month ago

      Bitwarden can’t be compared to KeePassXC. Bitwarden is fundamentally built around a sync server, whereas KeePass is meant to exclusively operate locally. These are two very different fundamental concepts for, you know, how to actually store and access your passwords.

        • unrushed233@lemmings.world
          0·
          1 month ago

          Nope. Since the entire database is contained in a single file, it can’t sync multiple edits properly, leading to sync conflicts. Because KeePass was built around local database files, whereas Bitwarden uses actual synced databases, where individual updates can be uploaded, instead of causing conflicts or overwriting the entire db.

          • Hexarei@programming.dev
            0·
            1 month ago

            Conflicts haven’t been an issue for years, all modern iterations of KeePass (XC, kp2a, DX) support automatically merging in the latest before saving.

            I’ve been using it for years this way across several devices, it’s incredibly solid

            • Dymonika@beehaw.org
              0·
              17 days ago

              Do you sync it across your devices using Syncthing? That’s what I’m thinking of doing.