Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

retrocomputing.stackexchange.com

Post reply on HN
Print view View original

41–50 of 111 posts

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

#41

Post by jacquesm »

cm2187 wrote: post #22
H8crilA wrote: post #19

Earlier quoted context omitted.

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 sup…

I remember those days. Even into the late 90s early 2000, modems (including ADSL) didn't come with a router, you had to establish a PPPoE connection from your computer, which also means your home machine was directly on the WAN with no firewall protection. I can't remember which version of windows but it must have been 98 or ME, you had to rush to download and install a patch when you connected it first to the intern…

> I can't remember which version of windows but it must have been 98 or ME, you had to rush to download and install a patch when you connected it first to the internet before one of these exploits would make it crash.

Even Win2K had that feature.

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

#42

Post by nikanj »

theclansman wrote: post #26
b800h wrote: post #6

This is proper programming. None of this namby-pamby web scripting that passes for development these days.

So many programming jobs feel like busy work with no interesting problems nowadays, I often wonder if it's only gonna get worse with time.

Are you telling me "Why do npm builds poop out 20% of the time" is not an interesting problem?

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

#43

Post by anthk »

Circuitstorm513 wrote: post #39
H8crilA wrote: post #19

Earlier quoted context omitted.

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 sup…

Earlier versions of Windows (98? 95?) also used to share things like drives (C$, D$) and printers with the dial-up connection by default. I remember connecting to a printer of a classmate over the internet and printing a page, to his surprise. All you needed was the IP, which was trivial to get from ICQ, back in the days.

Yeah, running an SMB/NFS scan gave you lots of fun on Modem/DSL connections.

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

#44

Post by wazoox »

cm2187 wrote: post #22
H8crilA wrote: post #19

Earlier quoted context omitted.

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 sup…

I remember those days. Even into the late 90s early 2000, modems (including ADSL) didn't come with a router, you had to establish a PPPoE connection from your computer, which also means your home machine was directly on the WAN with no firewall protection. I can't remember which version of windows but it must have been 98 or ME, you had to rush to download and install a patch when you connected it first to the intern…

IIRC Windows XP up to SP2 was vulnerable to this. Basically if you ran the install with the DSL modem attached, your PC was compromised even before the end of setup.

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

#48

Post by elzbardico »

underdeserver wrote: post #47

Why was the question asked and answered at the same timestamp?

To share the information. You'll see that the author of the question and the answer are the same person.

He probably decided that posting this info as a Q&A in SO would be more permanent than writing a blog post that would never be found by anyone.

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

#49

Post by flakes »

nikanj wrote: post #42
theclansman wrote: post #26

Earlier quoted context omitted.

So many programming jobs feel like busy work with no interesting problems nowadays, I often wonder if it's only gonna get worse with time.

Are you telling me "Why do npm builds poop out 20% of the time" is not an interesting problem?

Funny enough, I do actually find that interesting. Certainly not fixing your broken project, but, definitely designing package managers in general!

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

#50

Post by thelittleone »

aesegiopiuaer wrote: post #40
H8crilA wrote: post #19

Earlier quoted context omitted.

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 sup…

I remember when CdC released Back Orifice to remote control Windows machines, like ejecting CDROM and such [1]. We really did come a long way, where 0-days go for 20 million dollars. [2]. 1: https://en.wikipedia.org/wiki/Back_Orifice 2: https://techcrunch.com/2023/09/27/russian-zero-day-seller-of...

Could also disable certain keys on victims keyboard. Did that in the office a bunch was hilarious watching co workers who had no idea what was going on. Perfect for a Monday morning.
Post reply on HN