Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?

Re:Why does trying to break into the NT 3.1 kernel reboot my... by owenmarshall on Thursday September 28, 2023 @08:24AM (#37688599)

When W32/Blaster[0] came out I worked at a small ISP doing tech support and computer repair. A tech and I imaged an old box we had in the corner with a clean XP, assigned it a static IP in our /24, plugged it in and started a stopwatch. It didn’t even make it two minutes before it was infected.

[0] https://en.m.wikipedia.org/wiki/Blaster_(computer_worm)

[ Parent | on HN ]

Re:Why does trying to break into the NT 3.1 kernel reboot my... by eterm on Thursday September 28, 2023 @10:09AM (#37689823)

Yeah Blaster is one of the few worms I've ever (knowingly) been infected with. As you say, it was literally less than a minute or two between connecting an unpatched box and getting it.

[ Parent | on HN ]

Re:Why does trying to break into the NT 3.1 kernel reboot my... by pixl97 on Thursday September 28, 2023 @10:11AM (#37689853)

I was working for a small ISP in that time frame and that's when we started blocking incoming windows ports. And yea, it was annoying for the few techie types that tried to run SMB and could actually protect their stuff.

For the other 99.9% percent of the users it protected them and us.

Windows was such a mess back then.

[ Parent | on HN ]

Re:Why does trying to break into the NT 3.1 kernel reboot my... by jtbayly on Thursday September 28, 2023 @12:50PM (#37692305)

It took about 5 seconds IIRC on our college campus network.

[ Parent | on HN ]