Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
Okay thanks for mentionning overblown paranoia, that's what I have.
What kind of exploitable server misconfigurations are we talking about here?? Brute forcing won't work because fail2ban, right? I'm a noob and deep down I'm convinced that my homeserver is compromised and has beenpart of a bitcoin mining farm for years... Yet, not a single proof...
The very first Linux server I deployed on a VPS was hacked almost immediately because of my ignorance. The bot gained entrance, and they supplanted a miner rig. Now, on a tiny VPS, it's pretty easy to tell if you're running a coin miner because all of the resources will be pegged. However, I got to thinking, on a corporate server, if they did manage to do this, it would almost be undetectable until someone started reviewing logs.
Corporate servers will usually have some degree of SIEM implemented, and at least automatic audit log monitoring.
Aren't zero day very specific? Or maybe it's become a very generic term.
Anyway, I am under the impression that either it's suddenly very simple to hack into EVERYONE because someone zero dayed the wireguard protocol and there a major flow in it, it's a shitshow, for all, for some, just me or nobody, whatever. Or it's a very targeted attack on me personaly, and that's a whole other story and the means to protect my pictures of my cats and my cool public domain movies collection are different (think social engineering). Also port 22 being bombarded by brute force attempts so don't choose a password that's 6 letters thanks.
I KNOW I am missing many things, but still, I don't get it.
React2Shell is exactly the shitshow situation yes. Suddenly we are all at risk. But in this case, I'm sorry to say that my cats' pictures are worthless.
Your point on nginx/wireguard makes me think that it might be better to htaccess through a reverse proxy than relying on a built in login system. For exemple, I should deactivate jellyfin's login and put it behind an htaccess at the proxy's level. Is that completely dumb?
Anyway, I clearly need to research "threat models" and cyber/infosec more. Thank you very much!