It’s good to be paranoid when it comes to IT security (and software development). 👍

Listen.

Don’t expose any port to any service if you don’t need it.

If you do, make sure it’s as secure as you can reasonably make it.

I’m not disagreeing.

Sure, don’t open ports you don’t need. I said in a different here that I reject all expect IP ranges I’m in for home, mobile and work. That works for me. That blocks the vast majority of the world.

I agree with the other guy that I’m not a target for these vulnerabilities. They are rare and hard to exploit, and valuable. But the basic advice you give is good, obviously.

Don’t expose what you don’t need to expose. Still I have Immich and all of my photos on there. Good luck scamming me with threats of sending them to my family and work. 😀

Ah, now I remember. It took a quick configuration change to mitigate this. Still, I’d call this very rare.

I’m going side with @[email protected] on this one.

Well, those won’t typically have ssh exposed on them. But we could argue what is more risky to have exposed, ssh or http. Any publicly available server could be vulnerable, it’s just very unlikely these days (with up to date software).

I remember that one. Those are pretty rare and usually involve a specific configuration that is often not the default, though, right? When such a vulnerability is found, is it rightly so major news.

I have the firewall of my VPS reject any IP range except the ones I’m on frequently, that is mobile, home and work. Sucks when you travel, but otherwise works alright.

Still exposes ports to some people on the same mobile or home internet service networks…