Selfhosted

39664 readers

230 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

164

Why self host a password manager? (programming.dev)

submitted 1 week ago by [email protected] to c/selfhosted

159 comments fedilink hide all child comments

I'm going to move away from lastpass because the user experience is pretty fucking shit. I was going to look at 1pass as I use it a lot at work and so know it. However I have heard a lot of praise for BitWarden and VaultWarden on here and so probably going to try them out first.

My questions are to those of you who self-host, firstly: why?

And how do you mitigate the risk of your internet going down at home and blocking your access while away?

BitWarden's paid tier is only $10 a year which I'm happy to pay to support a decent service, but im curious about the benefits of the above. I already run syncthing on a pi so adding a password manager wouldn't need any additional hardware.

(page 3) 50 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 week ago (1 children)

Self-hosting removes the risk of somebody compromising Bitwarden’s servers and adding malicious javascript to send off your master password to a bad actor instead of just processing it locally like it’s designed to.

[–] [email protected] 1 points 1 week ago (1 children)

I think the chances of such a breach are vanishingly small. I wonder if I'm right though.

I think anyone capable of pulling off such a feat is not interested in my data, and probably more likely looking for government employee access etc..

[–] [email protected] 1 points 1 week ago

They don’t need to be interested though. You could conceivably dump all the password you collect in an attack and just start trying them automatically like you would any other breach. Find a bunch of bank accounts and your chances you getting away with millions are high. Not to mention: a breach like this means changing all your saved passwords to re-secure them which is a multi-day affair.

[–] [email protected] 1 points 1 week ago

Always self-host anything you can (reasonably).

In this case, don't self-host a password vault. Use a locally encrypted password storage app, and keep it in a self-hosted storage solution (which should also be encrypted).

People want to put too much shit online, opens you wide up for attempted hacking (especially if you use what everyone else uses).

[–] [email protected] 0 points 1 week ago (2 children)

Premium features for free. There are no benefits in relying on a third-party

[–] [email protected] 1 points 1 week ago

Well 'no benefits' is a bit of a stretch.

load more comments (1 replies)

load more comments