Selfhosted

40347 readers

330 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

182

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

submitted 9 months ago by MigratingtoLemmy@lemmy.world to c/selfhosted@lemmy.world

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

[–] Gooey0210@sh.itjust.works 7 points 9 months ago (6 children)

Notifications on system file access

Notifications on root login/sudo

Declarative OS, tmpfs root, disabled sudo

Bastion server, but right now I don't have a proper router to do it at home

Yubikey, or a separate phone on Graphene OS for otp, keys, etc

Authelia + fascist fail2ban (or some CSF)

Most of these are pretty normal, but usually you don't do them all at once 😄 also, I don't really like hiding my services from the open internet, authelia is fine tuned to let people only access what they are supposed to. And regular users of my server usually don't notice that I even have it

[–] SaintWacko@midwest.social 2 points 9 months ago* (last edited 9 months ago) (3 children)

I'd love to hear more about your Authelia setup. I'm using Authentik, but planning to do the same thing. I haven't opened my server up to the Internet yet (just built it on Friday), but what I'd like to do is have a webserver that supplies a login page, and you can't access anything else until you've logged in

[–] Gooey0210@sh.itjust.works 2 points 9 months ago (2 children)

I'm a Nixos user, I wouldn't be much help unless you do Nixos. But it's a whole new rabbit hole which would take you months/years to learn and setup 😅

What I can say, you can do "access from home network", "access from VPN network", "1fa/2fa from the internet" OR "access for / and /api, but 1fa/2fa for stuff like /admin, /admin-settings, or just /login or /logged-in"

Fail2ban is fun, also maybe have a look at crowdsec

[–] SaintWacko@midwest.social 1 points 9 months ago (1 children)

Ah, yeah, I'm running Proxmox. And I'm definitely seeing I have a lot of research to do before I open up to the internet!

[–] Gooey0210@sh.itjust.works 1 points 9 months ago

I'm actually not from the "close everything, don't open ports, always sit behind cloudflare" camp

We selfhost so we can use and share our services

There are other things we can practice instead of just isolationism and keeping everything as simple as possible

load more comments (2 replies)