Selfhosted

63,723 readers

5,179 active

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

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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

moderation log

moderators

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Systemd Service Hardening (roguesecurity.dev)

submitted 1 year ago by starkzarn@infosec.pub to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

This one is a little self-hosting specific, and more casual Linux best practices, but I've got a new blog post down for general security! Harden your systemd units (especially custom ones) for better peace of mind on the internet!

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

[–] starkzarn@infosec.pub [S] 3 points 1 year ago

Excellent! There's certainly a lot to unpack, but being able to twist all these little knobs is part of the beauty of Linux.

permalink

fedilink

source

parent