110
Bitwarden Switches to Commercial License (community.bitwarden.com)
submitted 1 month ago by to c/linux@programming.dev
24 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
[–] 44 points 1 month ago* (last edited 2 weeks ago) (4 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.

edit: Recently swapped out KeePassXC for ChiPass, a fork that has does not allow LLM use for development. It works fine with the same browser extension (which has a different LLM policy to the desktop client from my understanding), plus it works better with my system theme (running Niri + Noctalia, maybe Qt6 is better implemented in ChiPass? Not sure)

Either is fine, but I like ChiPass more for their stronger LLM policy (which means less shoddy code!) and the better theming. I also prefer ChiPass's icon (password boxes in a keyring) over KeePassXC's (...a key), if anything

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 6 points 1 month ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 1 point 1 month ago (1 child)
    [removed by mod]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 month 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.

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (-2 replies)
  • [–] 1 point 1 month ago (1 child)

    KeyGuard on Android can be a direct VaultWarden client.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 1 month ago* (last edited 1 month ago)

    KeyGuard is proprietary on Android. Certain features are locked behind a subscription or one time purchase.

    I'm starting to also hate on this model. People who claim to be open source but still throw hurdles and obstacles at anyone trying to either use or contribute to the project. I understand people need to support themselves financially, but I have donated to many free projects and open projects in my life. Whenever I see a paywall it makes me not want to use the project, however interesting it might be. It sucks they are usually the only almost decent android clients. (Looking at Symphonium and their developer's shit ass attitude too)

    EDIT: Just tried it and it seems like vaultwarden login and custom certificates on linux have been fried since December. It is currently a dead-end for selfhosters.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 0 points 1 month ago* (last edited 1 month ago) (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 9 points 1 month ago*

    Scratch that, maybe don't use Proton Pass. Just did some more searching, their CEO has donated millions of dollars to the Republican party. They also sponsored some alt-right French influencer (from my quick searching, a lot of racism, conspiracy, Holocaust denial, homophobia, transphobia, that sort). Yikes!

    My bad for not looking more into this!

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (-1 replies)