Conversation

joepie91 needs more railing 🚅💦 (🔜 eth0)

as I'm seeing more and more posts about people fearing self-hosting - and I can understand that if the responsibility of keeping things secure stresses you out, especially with the recent security patches - there's something you should probably know about that, that's maybe not quite obvious:

if you believe that you couldn't possibly reach the level of security of a professional operator, *don't*.

I have seen behind a lot of curtains. the professional/commercial operators of services have, on average, horrible security. they don't keep their software up-to-date, they dismiss legitimate security concerns, and they downplay or outright hide breaches. this applies to small and large operators alike, even big tech companies.

while there are some exceptions, the concept of "professionally run by security experts" in most cases just doesn't really exist outside of the marketing department. even in those companies which claim to be security-conscious! the security department is virtually always the first department to get cut, and if it exists at all they rarely have sufficient jurisdiction within the company to do their job properly.

so, I can entirely understand if you don't want the stress of hosting services and keeping them available and secure, it is genuinely a responsibility you take on towards others. but don't fear it out of the idea that you couldn't possibly meet the bar that commercial operators do, because they don't either, and they're usually running the same software that you do!

#selfhosting

3
1
2

@joepie91 genuinely you’ll probably will be better off than most non-tech companies with some sort of internet presence if you enable auto-update on everything you can and set a calendar task every week or two to check in on it (and update what doesn’t have auto update)

2
0
4

joepie91 needs more railing 🚅💦 (🔜 eth0)

@charlotte I don't think I'd even bother with the "non-tech" qualifier, to be honest. tech companies are usually only tech companies in that they really like adding more of it (tech), not necessarily thinking very hard about the implications of that.

1
0
2

Charlotte lotteheartplural/Cinny cinny_heart_plural thetadelta ursaminor treblesand

Edited 9 days ago

@joepie91 also something i would look into learning is really basic shell automation

can be as simple as stringing commands together like

set -euxo pipefail

apt update
apt upgrade

cd ~/docker/application1
docker compose pull
docker compose restart

.
.
.

the first line just tells the shell to say what is going to execute and then exits out early if something fails

0
0
2

@joepie91 yeah admittedly my workplace experiences are quite limited and the one company i have probably saved from lack of tech maintenance for who knows how long wasn’t a tech company but a construction company

1
0
3

@joepie91 they ran an extremely old PHP CMS that hasn’t been updated in years and didn’t have auto update

new versions did thankfully but there were signs of compromise. thankfully that site was on like a shared php webhost thing and only contained the internet presence of the company and no customer data

i upgraded their CMS to the latest version at the time, surprisingly nothing broke, and that has auto update

0
0
2

joepie91 needs more railing 🚅💦 (🔜 eth0)

@eater don't believe

0
0
1

@joepie91 I'm self hosting for a while now and my biggest fear is still that I just wouldn't notice if someone is in my network through whatever means đź’€

2
0
0

joepie91 needs more railing 🚅💦 (🔜 eth0)

@leberschnitzel it's a legitimate concern, but (tech and other) companies are routinely compromised for months without anyone noticing, so the bar is not high...

0
0
0
@leberschnitzel @joepie91 every once in a while i get a tiny heart attack about this and then i realised the chance of being compromised due to your fucking smart tv or iot fridge is *much* higher than some rando hacking into your ssh
0
1
0