Selfhosted

39947 readers

472 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:

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 1 year ago

MODERATORS

182

What are the most paranoid network/OS security measures you've implemented in your homelab? (self.selfhosted)

submitted 9 months ago by MigratingtoLemmy to c/selfhosted

132 comments fedilink hide all child comments

As the title says, I want to know the most paranoid security measures you've implemented in your homelab. I can think of SDN solutions with firewalls covering every interface, ACLs, locked-down/hardened OSes etc but not much beyond that. I'm wondering how deep this paranoia can go (and maybe even go down my own route too!).

Thanks!

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

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

I just use a pretty generic z-wave plug and home assistant. In the past I did more complex setups that actually determine what process is spiking and so forth. But eventually realized that "this is doing a lot of compute..." is a catch all for a LOT of potential issues.

And I guess I don't understand what you mean by "shouldn't be wireless". It is inherently going to be wireless because you will be on your phone on the other side of the planet. If you genuinely suspect you will be vulnerable to attacks of this scale then you.... probably have other things to worry about.

But as a safety blanket?

[–] [email protected] 1 points 9 months ago

Gotcha. A ZigBee/Z-wave plug was the first thing that came to mind. I'll probably go the same route. I was merely saying that wireless-anything is less dependable than wired. But I don't even know if wired smart plugs exist. I use wireless sensors around my home and I've never had an issue with dependability. I definitely wasn't considering Z-wave as a local attack vector. I was just brainstorming some way to avoid a wireless solution for something where dependability is paramount.