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.

you are viewing a single comment's thread
view the rest of the comments

[–] rozlav@lemmy.blahaj.zone 40 points 2 months ago (4 children)

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/

[–] Atemu@lemmy.ml 20 points 2 months 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 16 points 2 months ago (1 children)

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.

[–] Hexarei@programming.dev -1 points 2 months ago (1 children)

Store your database in a nextcloud instance and it's that too

[–] unrushed233@lemmings.world 2 points 2 months ago (1 children)

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 1 points 2 months ago (1 children)

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 2 points 1 month ago (1 children)

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

[–] Hexarei@programming.dev 1 points 1 month ago

I keep mine in a self hosted Nextcloud instance, DAV sync is built into the app

[–] EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 10 points 2 months ago* (last edited 2 months 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.

[–] AustralianSimon@lemmy.world 3 points 2 months ago (2 children)

No Android app though?

[–] piracysails@lemm.ee 11 points 2 months ago* (last edited 2 months ago) (1 children)

KeepassDX

[–] AustralianSimon@lemmy.world 4 points 2 months ago

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.

[–] SquiffSquiff@lemmy.world 5 points 2 months ago (1 children)

keepass2android

[–] AustralianSimon@lemmy.world 1 points 2 months ago (1 children)

No excuse to not look into it now. Hopefully it uses Android autofill.

[–] fossphi@lemm.ee 1 points 2 months ago (1 children)

It does support autofill

[–] AustralianSimon@lemmy.world 1 points 2 months ago

Testing it then will see if it passes the wife test for ease of use.