Selfhosted

40202 readers

509 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] 6 points 9 months ago* (last edited 9 months ago) (7 children)

full disk encryption on everything except the router (no point in encrypting the router)
- the server doesn't have a display connected for obvious reasons, so I'm manually unlocking it via ssh on each boot
  - obviously, the SSH keys are different, so the server has a different IP in initrd. That said, I still don't have any protection against malicious modification of initrd or UEFI
the server scans all new SSL certificates in realtime using certspotter and notifies me of any new certificates issued for my domains that it doesn't know about (I use Cloudflare so it triggers relatively often, but I still do checks on who the issuer is)
firewall blocks outgoing 25 so nobody can impersonate my mailserver

[–] refreeze 1 points 9 months ago (3 children)

You might be interested in setting up network bound encryption via Clevis and Tang. I use a hidden pi zero in my house acting as a Tang server. It's great being able to reboot any of my encrypted servers without having to manually unlock disks.

[–] tapdattl 2 points 9 months ago (1 children)

Do you recommend any resources about this? I'd be interested in learning how to implement this.

[–] refreeze 2 points 9 months ago

I'm using the recently merged Clevis module for NixOS. There was a recent talk at FOSDEM about it.

load more comments (1 replies)

load more comments (4 replies)