Selfhosted

60664 readers

765 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

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What actual damage do you secure your servers against? Whats the attack vector? (lemmy.ca)

submitted 1 week ago by lambdabeta@lemmy.ca to c/selfhosted@lemmy.world

41 comments fedilink hide all child comments

I'm a software developer working in the telecam sector on security related products, so I know a fair bit about system security. Yet I wound secure my own system far less than most people here if I didn't enjoy cybersecurity as a hobby.

I wonder what you are securing against? Some examples:

jellyfin: unless you have home videos on there, what does it matter if someone exfiltrates some movies? Surely you have basic DOS protection and/or region locking to reduce wasted network traffic, right?
linux: I assume nobody is using their servers as daily drive PCs, so what does it matter if somehow your system is superficially compromised. You can always reimage. Sure they could mine some bitcoin with your system, but it doesn't have that much PSU headroom to cost you much on your bills, right?

It just seems like most attack vectors lead to mild annoyance at most for most systems.

Do you guys just enjoy cybersecurity? Do you actually keep sensitive data on your self hosted systems? Do you self-host on expensive hardware? What am I missing?

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

[–] placebo@lemmy.zip 3 points 1 week ago* (last edited 1 week ago) (1 children)

Do you actually keep sensitive data on your self hosted systems?

People self-host photos, documents, code, passwords, chats, and other sensitive stuff. Even Jellyfin in your example can get you into legal troubles if your pirated (or even legally obtained and ripped) content suddenly becomes public.

What am I missing?

That it's 2026 and our lives are heavily digitalized. I'd understand this question in 2000 where you'd probably host a few html files and a counter-strike server, but come on.

[–] lambdabeta@lemmy.ca 1 points 2 days ago

Fair. I guess what really prompted this question was a chat with a "normie" relative who was self-hosting jellyfin on their main computer, no security (username: user, password: pass, SSL: disabled). I had to explain all the issues (even no fail2ban on their server with an exposed port 22). They thought I was paranoid. But even my suggestions weren't as extreme as many people put.