this post was submitted on 20 Aug 2024
64 points (97.1% liked)

Selfhosted

39905 readers
379 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
64
What do you guys do about usernames / passwords for your local services? (lemmy.world)
submitted 2 months ago by [email protected] to c/[email protected]
83 comments fedilink hide all child comments
 

Basically every local service is accessed via a web interface, and every interface wants a username and password. Assuming none of these services are exposed to the internet, how much effort do you put into security here?
Personally, I didn't really think about it when I started. I make a half-assed effort at security where I don't use "admin" or anything obvious as the username, and I use a decent-but-not-industrial password - but I started reusing the u/p as the number of services I'm running grew. I have my browsers remember the u/ps.
Should one go farther than this? And if so, what's the threat model? Is there an easier way?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 60 points 2 months ago* (last edited 2 months ago) (38 children)

Public-facing: Password generator, stored in a password manager.

Internal LAN: Everything gets the same re-used, low-effort password.

Nobody is going to hack my CUPS server.

[–] [email protected] -3 points 2 months ago (36 children)

But if they do, they have every password for all your stuff. hopefutlly you have Ipv6 disabled

[–] [email protected] 8 points 2 months ago (18 children)

IPv6 should not be disabled under any circumstances.

In fact, many devices in my house have IPv4 disabled. Disabling IPv4 on my public-facing SSH reduced the attack traffic to zero.

IPv4 is shit.

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

IPv6 was just found to have a critical exploit, and the solution is to disable it.

[–] [email protected] 25 points 2 months ago (2 children)

I'm pretty sure that vulnerability only affected windows machines. Surely you're not running a homelab with windows server?

[–] [email protected] 3 points 2 months ago

Wouldn’t any windows device in your network be vulnerable? And from there everything else.

[–] [email protected] 4 points 2 months ago (1 children)

The only windows machine on my home network is the backup Windows laptop that I only boot when I need to run something like Odin to flash a tablet or some niche Nintendo switch management software.

load more comments (15 replies)
load more comments (32 replies)
load more comments (33 replies)