Published version update in app stores
community.bitwarden.com
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...

cross-posted from: https://thelemmy.club/post/57178743

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
    • mbirth 🇬🇧@lemmy.mlEnglish
      4·
      11 hours ago

      I’m using Strongbox on macOS and iOS. Uses a KeePass2 database in the background, does TOTP (so does KeePassXC), syncs via iCloud (but also supports SFTP, WebDAV, OneDrive, Google Drive, and Dropbox) and also keeps my Passkeys. And it supports Apple’s AutoFill API, so it works in basically any input field across the systems and feels “native”. No browser extensions (at least for Safari) needed.

      And if it goes rogue, I can switch to e.g. KeePassium or any other KeePass-compatible app.

    • Foni@piefed.zipEnglish
      41·
      10 hours ago

      I might be a bit paranoid (or an idiot) but I think having the password and the totp in the same database (and app) somewhat negates the point of two-factor authentication.

      • devfuuu@lemmy.worldEnglish
        11·
        8 hours ago

        It does negate the big issue of passwords leaking from the websites and that’s the most important part of even having totp.

        Nobody is going to spend time to separate the 2 and maintain backups of two different things and all that extra effort when 90% of people don’t even use password managers.

        Don’t let perfection be the enemy of improvement.