Default passwords, old insecure versions of apps and system packages, etc. “Just getting it working” usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services.
Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That’s fine if you don’t expose anything to the internet, so keep that surface area as limited as possible.
sugar_in_your_tea@sh.itjust.works 3 weeks ago
Default passwords, old insecure versions of apps and system packages, etc. “Just getting it working” usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services.
SheeEttin@lemmy.zip 3 weeks ago
Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall.
sugar_in_your_tea@sh.itjust.works 3 weeks ago
Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That’s fine if you don’t expose anything to the internet, so keep that surface area as limited as possible.