4mo ago

Bitwarden Desktop version 2024.10.0 is no longer free software

github.com Desktop version 2024.10.0 is no longer free software · Issue #11611 · bitwarden/clients

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.

Opensource @programming.dev

Blaze @lemmy.zip

4mo ago

Desktop version 2024.10.0 is no longer free software · Issue #11611 · bitwarden/clients

github.com /bitwarden/clients/issues/11611

22 0

Linux @lemmy.ml

tifriis @sh.itjust.works

4mo ago

Desktop version 2024.10.0 is no longer free software · Issue #11611 · bitwarden/clients · GitHub

github.com /bitwarden/clients/issues/11611

235 18

Privacy @programming.dev

lemme in @lemm.ee

4mo ago

Desktop version 2024.10.0 is no longer free software · Issue #11611 · bitwarden/clients

github.com /bitwarden/clients/issues/11611

77 10

You're viewing a single thread.

126 comments

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/
- 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.
- 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.
  
  Store your database in a nextcloud instance and it's that too
  
  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.
  
  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
  
  Do you sync it across your devices using Syncthing? That's what I'm thinking of doing.
  
  I keep mine in a self hosted Nextcloud instance, DAV sync is built into the app
- 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.
- No Android app though?
  
  KeepassDX
  
  Ty, exploring alternative tools. I really don't like last pass due to their lax data security and 1 Password for the same reason.
  Bitwarden still earns my $10/year.
  
  keepass2android
  
  No excuse to not look into it now. Hopefully it uses Android autofill.
  
  It does support autofill
  
  Testing it then will see if it passes the wife test for ease of use.

126 comments