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

[–] umbrella@lemmy.ml 12 points 2 months ago* (last edited 2 months ago) (1 children)

i was about to replace my glorified encrypted text file for a password manager. guess relying on 3rd parties in a late-stage capitalist world is not a viable alternative.

ill stay with my encrypted text file until they privatize encryption. by then ill probably be carving my passwords out on stone. or burning down the servers of these fucking pigs trying to make us identify ourselves for everything on the internet now.

[–] EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 12 points 2 months ago (1 children)

KeePassXC is pretty amazing. :)

[–] umbrella@lemmy.ml 2 points 2 months ago (3 children)

can u selfhost it?

[–] EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 12 points 2 months ago* (last edited 2 months ago)

I would assume so. According to the page Documentation and FAQ,

Why is there no cloud synchronization feature built into KeePassXC?

Cloud synchronization with Dropbox, Google Drive, OneDrive, ownCloud, Nextcloud etc. can be easily accomplished by simply storing your KeePassXC database inside your shared cloud folder and letting your synchronization service of choice do the rest. We prefer this approach, because it is simple, not tied to a specific cloud provider and keeps the complexity of our code low.

[–] pressanykeynow@lemmy.world 11 points 2 months ago

It's basically your encrypted file, you are to handle synchronisation yourself.