- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
If you are interested in privacy you are probably interested in password storage … plus I wanted everyone to know about the inevitable future enshitification of this product. Spread the word and replacement recommendations are welcome too.
You must log in or register to comment.
This is really disappointing… I figured the open source nature of Bitwarden would save it from enshittification but as the author says, in the end, the company doesn’t need to keep it open source.
As soon as VC money comes in, the founders cash out and the enshittification begins as the VC will be expecting returns on their money.
Vaultwarden will survive. Since the client is open source, once they close the API and break compatibility of the clients with Vaultwarden, the old version of the app can simply be forked and rebranded. I also do hope that the KeyGuard app will continue to support vaultwarden as well since if bitwarden closes the API and makes a breaking change, as is likely to happen, it will break KeyGuard as well, but it will still work with VaultWarden for some time.
The real issue is that many people who are using Bitwarden aren’t savvy enough to host Vaultwarden in a secure way. Many people are careless with things like secret keys and such and dont know how to properly secure a web facing app or a VPN into their local network. But anyone who self hosts should result learn those things anyway. This one just happens to be a particularly high risk since it contains all of your passwords for everything else.
We really need a VaultWarden paid service, if there isn’t anything against doing so in the license.
I don’t know why the server needs any specialized software at all though. In the end, if it’s just some password history, why not just have a client that allows generic storage backends and you can upload to Filen or S3 or whatever else you use?
This is why despite me self hosting some things I don’t rely on vaultwarden. I’m a flawed person and my family has no idea about anything. I don’t need to stretch my imagination very far to think of a handful of reasons why it would fail my situation. I’ll gladly pay for a password manager to not have to deal with that.
Same! I self host a number of things, but I just didn’t trust myself with something as important as this. I had been paying for bitwarden even though the free plan was sufficient, just to show support. But obviously not if they go this route. I will also gladly pay for a password manager to not have to deal with that.
I still wish there was something where it had better syncing conflict management than KeePass but wouldn’t make you unable to do anything or randomly make your passwords completely inaccessible if you or your server went offline like Bitwarden.
I run vaultwarden at home without access to it from the outside world and once the sync is done I can be offline without issue.
if you were looking for an excuse to torpedo this abomination, here it is. hosting this gargantuan stack just for an encrypted csv file? at least the client (electron) gobbles up RAM like it’s free while being bug-compatible with whatever chrome version was current half a year ago.
sadly, news ain’t great on the other side of the fence - keepassXC dev is all-in on vibeshitting; latest non-polluted version is 2.7.9.; works fine and the stuff they’re working on is pretty far from essential. some unknown folks forked it but who’s to say what their expertise is.
never thought I’d disable my autoupdate timers but here we are. keep your eyes open.
Can you explain the issues with KeePass? Or is there another thread?
the dev vibecodes; I make a distinction between using the crap as a boilerplate helper and a full-blown agentic “hey computer, do this but do it super-good!”. not only that, they got a super-asshole vibe as they removed claude traces from the repo and then flaunted that it’s so people won’t know what parts were vibeshat. “good luck finding the cutoff point”, I’m paraphrasing here.
to each their own, but that’s a hard pass for that fork from me.
A password manager is literally the poster child for “I would rather it lack features, but be built carefully by an expert.”
Time to recommend alternatives?!
Nothing has beaten KeePass for me so far. It takes a bit of setting up if you want your database to sync among all your devices, but in other aspects it’s perfect for me
EDIT: In case you’re curious, I use KeePassXC on PC, KeePassDX on Android, and Syncthing to sync the database.
What drove me (and my family) from KeePass to Bitwarden was the family sharing and survivor access.
Until KeePass supports these it’s not really up to par with Bitwarden.
Especially digital legacy management is a must have for a well rounded password manager.
Why the hell is anyone using anything other than KeePass?
Doesn’t keepass only work on a single device? Meaning that you have to handle syncing the database file yourself. I prefer selfhosting vaultwarden. Maybe these changes will make me migrate to something else but for now I’m very satisfied with vaultwarden and the bitwarden client.
I just tested aliasvault and its pretty good. You can even just import your pre-enshitification Vaultwarden export file.
One thing I noticed though is that your entries must have a collection or else they don’t export. But close to easy as pie to leave vaultwarden behind with their Nazi CEO.
VaultWarden != BitWarden!
I know. Either way I’m out unless they fork.
VaultWarden literally is a fork, what are you on about?
VaiultWarden is a new implementation of the Bitwarden API. It started from scratch, never was a fork. It’s possible they (or other people) will fork the Bitwarden client.
Fork means they don’t share. But its not like that.
Are you a bot? It doesn’t seem like you understand what you’re talking about.
They website says they are not but there’s is an employee of bitwarden who is allowed to contributed.
I don’t know. I will be on my toes at any notion of Nazi CEO contribution or attribution.
Again, vaultwarden is not bitwarden, I think I’m having a stroke reading this
