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.

(page 3) 30 comments

sorted by: hot top controversial new old

[–] fireshell@lemmy.ml 2 points 1 month ago* (last edited 1 month ago) (2 children)

pass is enough (+ xdotool + rofi + pass-menu). Synchronization via git or Syncthing.

[–] guillem@aussie.zone 1 points 1 month ago (2 children)

I'm familiar with pass and familiar-ish with rofi. What do the other two do?

load more comments (2 replies)

[–] tetris11@lemmy.ml 1 points 1 month ago (6 children)

How does this play with mobile?

load more comments (6 replies)

[–] preasket@lemy.lol 0 points 1 month ago

We need a fully community run password manager with row-level server synchronisation between devices and shared vaults. Maybe a new client for the Bitwarden protocol with Vaultwarden or something new. E.g. 1password's secret key as a second factor is, imho, their best feature. It pretty much eliminates the possibility of the vault being decrypted due to a weak master password.

load more comments