Selfhosted

59999 readers

734 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Reevaluating my password management (sh.itjust.works)

submitted 11 months ago by muusemuuse@sh.itjust.works to c/selfhosted@lemmy.world

65 comments fedilink hide all child comments

It never made sense to me to put password managers in the cloud. Regards to what you intend it to do, you’re making it accessible to a wider audience than necessary. And yet, I’m using iCloud. It’s time for a change.

I’m thinking of just running a locally hosted password manager on my home server and letting my devices sync with it somehow when I’m at home. I have a VPN into my home network when I’m away that automatically triggers when I leave the house, so even that’s not that big an issue, but I’m really not familiar with what’s gonna cleanly integrate with all my stuff and be easy to use. All I know is I wanna kill the cloud functionality of my setup.

I already have a jellyfish server so I figured I would just throw this onto that. Any suggestions?

you are viewing a single comment's thread
view the rest of the comments

[–] kebab@endlesstalk.org 2 points 11 months ago (1 children)

What’s the issue of exposing this one to the internet? Even if the database gets leaked somehow, your passwords are still protected by a hopefully strong master password + strong encryption

[–] dis_honestfamiliar@lemmy.sdf.org 1 points 11 months ago (1 children)

I guess it's due to unnecessary risk and lazyness of not wanting to get a domain for TLS. Mostly the unnecessary risk, like why expose it when I don't have to.

[–] kebab@endlesstalk.org 3 points 11 months ago

Because it lets you sync your passwords anytime, without having to connect to the VPN first, which saves time. And the risk of data leak is not really there since the passwords are encrypted by a strong master password anyways. With Vaultwarden, you can host your database even publicly and share it on Lemmy and nothing would happen, provided you use a strong master password, which you definitely should.