6 ms·
Bitwarden is still excellent, but keep an eye on them over the next few years. Remember that Bitwarden was originally a LastPass alternative without the fuckery
by jdlyga 2y ago
Bitwarden is still excellent, but keep an eye on them over the next few years. Remember that Bitwarden was originally a LastPass alternative without the fuckery.
- deleted 2y ago[deleted]
- odo1242 2y agoI mean, it still is. It’s honestly gotten better too - for evidence, it’s the one password manager that never gets recommended by sponsored YouTubers but always gets recommended by non-sponsored YouTubers.
- afavour 2y agoIt depresses me that Bitwarden has also taken VC funding, just like 1Password. It’s still a great product but as with any VC product I’m just waiting for the other shoe to drop when it’s revenue generation time.
- KPGv2 2y agoI honestly don't think the password manager market could bear more than $3–5/mo for an individual user or family. I used 1Password for years until they went from one-time payment to monthly sub and removed local sync so you could only use multiple devices by paying them. I think a big decision there was that they wanted $10/mo or something. I can't remember, but at the time it seemed ludicrous. Years later, when my new laptop couldn't run the final local-sync version of 1Password, I finally decide to look into password managers again, and lo and behold $3/mo. I signed up immediately.
- prophesi 2y agoThe LastPass fuckery was long and frankly egregious. Though I don't understand why this git commit is what's linked here. I'd rather hear the discussions on it. https://github.com/bitwarden/clients/issues/11611 https://github.com/bitwarden/clients/issues/11611
- hnbad 2y agoAfter reading through the issue thread and the final reply by Bitwarden, I think the only context this provides is that the headline should rather be something like "Bitwarden SDK fixes dependency licensing issue". The opening comment and the final reply are the only valuable contributions in that issue. Everything in between is random people jumping in to feign outrage or telling people to use Vaultwarden (which btw recently was in the news for more significant negative reasons). If anything it's a perfect example of the sad state of online discourse.
- ferbivore 2y agoThis wasn't an "issue", it was working as intended. The GPLv3 client intentionally depended on proprietary code. The CTO's comments on bitwarden/clients#11611, bitwarden/sdk#898 and fdroid/fdroiddata!15353 make it clear this was deliberate. They've now changed their stance because of the backlash. It looks to me like people expressed genuine concerns about being lied to by a company, one they'd trusted with their passwords no less. Calling it "feigned outrage" is a bit rude.
- kevincox 2y agoReal links for easy clicking: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15353 https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15353 https://github.com/bitwarden/clients/issues/11611 https://github.com/bitwarden/clients/issues/11611
- SirGiggles 2y ago> (which btw recently was in the news for more significant negative reasons) Do you by chance mean CVE-2024-{39924, 39925, 39926}?
- hedora 2y agoInterestingly, none of those impact me, since they involve an authenticated attacker. I trust all the users that can log into my vaultwarden instance. Were there any other recent issues?
- throwaway918299 2y agoDespite being proprietary, 1Password still hasn’t had any fuckery that I am aware of. I have been tempted to switch to an open source solution many times but I think I’ll be parking right here for a few more years yet.