Break as in Ctrl+C
Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
11–20 of 111 posts
Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#12I build a port check way back to determine if services are up. It crashed half the company by simply opening a few tcp ports to the machines. Ridiculous days :)
sounds like it was more than "a few"
Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#13This is proper programming. None of this namby-pamby web scripting that passes for development these days.
Sir we program in YAML exclusively now.
Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#14Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#15Don't forget to read the how buried in the hidden comments at the end!
Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#16This is proper programming. None of this namby-pamby web scripting that passes for development these days.
[deleted]
Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#17"The fix is obvious" indeed.
Well, once the bug is identified, yes. I wonder how do you find a bug like that, I guess you keep reading the disassembly of the trapping code until you find the problem. I don't think he could have used QEMU or some other form of debugging.
Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#18Re: Why does trying to break into the NT 3.1 kernel reboot my 486DX4 machine?
#19I build a port check way back to determine if services are up. It crashed half the company by simply opening a few tcp ports to the machines. Ridiculous days :)
Remember when Win95 could be crashed or even rooted just by pinging it the right way? We really have come a long way.
https://en.wikipedia.org/wiki/Ping_of_death
I also remember SMB vulnerabilities that stayed unpatched for years on some machines. That was already when Metasploit existed, so you could inject VNC into most Windows hosts on local network with just a few commands. These days at least the patching is super fast.