@[email protected] to Selfhosted • 7 months agoWhat are common practice's for hardening/securing your server?message-square66fedilinkarrow-up1139arrow-down12
arrow-up1137arrow-down1message-squareWhat are common practice's for hardening/securing your server?@[email protected] to Selfhosted • 7 months agomessage-square66fedilink
minus-squarePossibly linuxlinkfedilinkEnglish1•7 months agoIt is if you are defending against automation.
minus-square@[email protected]linkfedilinkEnglish2•7 months agoIt defends against the lowest level of automation. And if that is a legit threat in your model, you are going to have a bad time. It’s just going to trip you up at some point
minus-squarePossibly linuxlinkfedilinkEnglish1•7 months agoI’m not saying it should be your only defense. I’m saying that changing defaults is a good idea for secure systems. For instance, you should change the default WiFi password on your router.
minus-squarePossibly linuxlinkfedilinkEnglish0•7 months agoSo is changing the port. It won’t do a lot in terms of security but it will help a tiny bit
Security by obscurity is no security.
It is if you are defending against automation.
It defends against the lowest level of automation. And if that is a legit threat in your model, you are going to have a bad time.
It’s just going to trip you up at some point
I’m not saying it should be your only defense. I’m saying that changing defaults is a good idea for secure systems.
For instance, you should change the default WiFi password on your router.
Yes, because a password is security
So is changing the port. It won’t do a lot in terms of security but it will help a tiny bit