538

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) 29 comments
sorted by: hot top controversial new old
[-] fireshell@lemmy.ml 2 points 2 months ago* (last edited 2 months ago)

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

[-] guillem@aussie.zone 1 points 2 months ago

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 2 months ago

How does this play with mobile?

load more comments (6 replies)
[-] preasket@lemy.lol 1 points 2 months 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
view more: ‹ prev next ›
this post was submitted on 20 Oct 2024
538 points (95.6% liked)

Open Source

31759 readers
197 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS