Linux

15173 readers

240 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

Bitwarden Switches to Commercial License (community.bitwarden.com)

submitted 15 hours ago by Mustachius_Grumpius@thelemmy.club to c/linux@programming.dev

17 comments fedilink hide all child comments

RyanL Bitwarden Employee

Hello everyone!

Starting in the next release, the Bitwarden apps published to the various stores will be the commercially licensed builds. No action is needed, and the apps will work exactly as they do today.

Bitwarden remains committed to open source security and transparency
The GPLv3 OSS licensed version continues to be updated and published on GitHub
All current features are available in both versions
License details are on GitHub
Bitwarden remains committed to a robust, free forever plan for everyone

If you have any questions, please ask them in this thread. Thanks all!

EDIT:

Bitwarden is not going closed-source
You can still fork Bitwarden
No change to self-hosting, the licensing change affects those who are repackaging and reselling Bitwarden
The free plan is here to stay permanently

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

[–] scallisto@retrofed.com 33 points 14 hours ago (3 children)

From reading the thread, it looks like they are dodging the question of what features will be restricted to the commercial license versions ("case-by-case basis" apparently). They keep repeating "no change to people using the app currently", "no change to self-hosting right now", etc., but it doesn't inspire confidence.

I would recommend to read the thread and ask questions there if you have any, but I would definitely have a backup plan ready.

The KeePass ecosystem is awesome and it's what I use, it's local-first and you can use Syncthing to have passwords across many devices. KeePassXC for desktop (+ browser extension if you need it), KeePassDX on Android (w/ Syncthing-fork), and if you use iOS, you have KeePassium and Strongbox (w/ Synctrain). The iOS apps are more limited, blame Apple for their restrictive ecosystem and high entry fee.

[–] scott@lem.free.as 2 points 7 hours ago

KeyGuard on Android can be a direct VaultWarden client.

[–] scallisto@retrofed.com 8 points 14 hours ago (1 children)

Secrets is another decent KeePass client and works well with Gnome and other desktops that work well with libadwaita. It doesn't have browser integration though, so it's a non-starter for me.

[–] MangoCats@feddit.it 1 points 13 hours ago (1 children)

How, if at all, does this change impact Vaultwarden?

[–] TVA@thebrainbin.org 1 points 12 hours ago

VaultWarden is already it's own thing code base wise, so, it likely won't effect the hosted portion of it at all.

The apps though, sounds like right now, it sounds like it won't make a difference, but, I think moving forwards it'd make sense to consider forking and making VW branded versions.

With that said, right now, the only reason you can choose your own domain is because BW allows you to self host their own product and VW just made their API respond the same way as BWs, so, as long as BW keeps allowing the self host option, I would imagine that there really isn't much they can do about VW other than starting to play games with their API, which would also impact their paying customers.