Mastodawn

Another new Let's Encrypt-secured website, another case of getting 82 hacking attempts in the first 30 seconds after it came online for the first time ever.

Do. Not. Kid. Yourself. "Oh, I'll delete the config files once I get it working." "Eh, I'm just some nobody. Who's going to care?" Yeah, I'll tell you who: people who watch for new sites come online and then immediately slam them with hacking probes.

"I'll get to it soon" means you better do it within 3 seconds.

https://honeypot.net/2024/05/16/i-am-not.html

Honeypot.net

I am not exaggerating this: I created a new hostname in DNS, …

Show thread

Markus Peuhkuri

Years ago, a student put a Raspberry Pi with default account and password to public IP address with very little filtering. It took 23 seconds after bootup before someone logged in unauthorized via ssh. And that IP most likely had some other system before that, so it was just random IP scanning.
Now as any https site existence is revealed via transparency logs (not only LE), it is immediate.
Have a access control (firewall or server config) if you need some changes before going fully live.
@tek