Bitwarden: Avoid at all costs (outage issue)
71–80 of 137 posts
Re: Bitwarden: Avoid at all costs (outage issue)
#72Re: Bitwarden: Avoid at all costs (outage issue)
#73Earlier quoted context omitted.
You're one of the anon-Bitwarden boys? 1) I want sane error messages on the client side. 2) I want my feedback on community forums not to be shushed. You screwed up — own it. Community mods aren't janitors to wipe out user feedback. 3) I want the extension to be working no matter what kind of server-side problems you have. Let me know about a sync problem but don't terminate my access. But if you do think, that for $…
Idk why you think you should be able to login to a cloud SaaS product while its down. From your comment here I highly highly doubt you were at all even remotely civil in that forum post $12 a month doesn't mean you get to be an asshole to people. Not all forms of Auth can be done locally, for example most 2fa requires server access.
Re: Bitwarden: Avoid at all costs (outage issue)
#74Earlier quoted context omitted.
There is no lock-in to Bitwarden, stop spreading FUD. I'm not really sure how long this is going to be like this with the VC money, but right now: - Everything is open source - You get to self host - You get to export your database at any time - You don't even need to pay to use it if you don't want to Are local password managers objectively more secure and reliable? Yes. Does that mean that Bitwarden is just an awfu…
Let me quote some excerpts from their license FAQ[0]: > With respect to the server software available under the Bitwarden License, production use requires a separate commercial agreement with Bitwarden > The right to use the software in a production environment, or environments directly supporting production, requires a paid Bitwarden subscription > The Bitwarden License does not qualify as an open source license und…
Also Bitwarden's software has multiple licenses, one of them being AGPL for the server and one of them being GPL for the client. The part of the code that's under the Bitwarden license which you have to pay for is SSO, SCIM and I think FIDO2 authentication as they use some Azure tools for all of these and as such they can't run on premises
Quoting from their license FAQ [1]:
> "In your GitHub repositories, how can I determine what license applies to a given software program?"
> "Each Bitwarden repository contains a LICENSE.txt file that spells out which license applies to the code in that repository."
> "In the case of the Bitwarden server repository, the files are organized into various directories. These directories are not only used for logical code organization, but also to clearly distinguish the license that a given source file falls under. All source files under the /bitwarden_license directory at the root of the server repository are subject to the Bitwarden License. If a file is not organized under the /bitwarden_license directory, the AGPL 3.0 license applies."
Vaultwarden offers those for free if you so wish, but there are no restrictions to self hosting Bitwarden.
[0]: https://github.com/dani-garcia/vaultwarden
[1]: https://github.com/bitwarden/server/blob/master/LICENSE_FAQ....
Re: Bitwarden: Avoid at all costs (outage issue)
#75Yes, Syncthing doesn't work on iphone, buy your mother an android , or buy yourself a tie machine and write apps for windows Phone
Re: Bitwarden: Avoid at all costs (outage issue)
#76Earlier quoted context omitted.
It's a closed-source UI on top of sqlite/SQLCipher. You'll be fine.
I mean sure... But why go out of my way to use closed source software when the open source options are right there?
Re: Bitwarden: Avoid at all costs (outage issue)
#77Earlier quoted context omitted.
Or just use KeePassXC+nextcloud/syncthing as others have suggested, it's just an encrypted database with no cloud bullshit.
Can you please explain why this is an improvement over the parent comment solution?
Re: Bitwarden: Avoid at all costs (outage issue)
#78I'm sorry, but isn't the highlight of your problem is that you did not separate TOTP with any service that depends on it, including BW?
Re: Bitwarden: Avoid at all costs (outage issue)
#79Earlier quoted context omitted.
Another options is pass [0], which uses GPG to encrypt your stuff. Everything happens through the CLI but there are also GUI frontends for it. There's also gopass [1] which is very similar and compatible but does some extra stuff such as versioning with git. Similarly to this API compatibility there's KeePassDX [2] for mobile phones which is compatible with the KeePass database format. There's also KeePass [3] which…
I didn't find the sync that hard with pass and iOS (I'm sure Android has something equivalent): Set up a private git repo somewhere and configure passforios to pull from it. I have been running it for a few months now and it's smooth. This assumes you are on Linux or Mac.