Slashdot Mirror
Code Red III
drcrja was the first to send us this brief bit about Code Red III which is apparently faster and more vicious than its entertaining predecessors. I'm still wondering what I should do with the hundreds of IPs in my desktop's apache log trying hopelessly to overflow my buffer.
What the hell is a bigger backdoor?
You can find the definitive answer to that question here
One's socket after being rampaged with a big stick?
Well, that is one possibility...
Python has no buffer overflow problems. Neither does Perl. Okay, so .... what does that tell you? Is this something that has "always been a problem in people's code."? Or is it something in the C library that encourages buffer overflows?
-russ
Don't piss off The Angry Economist
And by the way, Coward, I'm a junior computer science & engineering major at a well-respected private university where I am the chairman of the Association for Computing Machinery (ACM). I also have a high IQ and don't hesitate to arrogantly and effectively deal with scum like yourself.
Have a nice day :-D
If you celebrate Xmas, befriend me (538
Ok.
IIS with the latest patches is uncrackable, unhackable, un/.able. Woe to any who try.
IIS beats Apache like a pimp beatin' his
ho. All you hackers, crackers and snackers,
don't even try to mess with IIS. It's impossible.
Shut up cockbiter: You just finish your Grade 11 computer class so you had to run to Slashdot to show your brilliance? It's pretty fucking amazing that you know what the acronym IP stands for.
For your information pillowbiter, in general context "IP" is used as a shortform for "IP Address". Get used to it on this new fangled "Internet" thing.
Code Red I, II, and III are pretty dull names. Why not call II and III something like Code Blue or Code Monkey or something.
Got Rhinos?
If Microsoft can't even patch their own servers then how can anyone expect others to do it properly? The best solution (in the long run), is to switch to a server which has less vulnerabilities.
Developers: We can use your help.
I know gun manufacturers shouldn't be sued when someone commits a crime with a firearm, and in that case the people who created the lame Code Red virii should be sued primarily, but I still think Microsoft is guilty here because their customers weren't aware their Windows-running boxes could start chewing up bandwidth like crazy simply because the OS vendor doesn't give a damn about these things.
To my knowledge, Microsoft didn't even try to mass-mail the patch to their registered customers who might be affected. Therefore, at the very least, I reckon they should be ordered to pay damages to telcos and ISPs for lack of due diligence.
(of course, in Georgia, I'd also be happy to see the state sue them for 59c per second of wasted bandwidth as well :-)
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Yeah, like formatting an active partition will work. Loser.
I think this is really fun. Of course I am not an ISP or anything. Anyway, I am looking forward to a nice DDOS of whitehouse.gov this time around. That'd be fun wouldn't it? This is some nice distributed computing :) Has there ever been a virus so widespread as Code Red X ? Is this going to be the future of virus writing? Imagine something similar being written for routers? By the way, is it possible to write a virus that can't be decoded by the spoilers over at Eeye and all you old programmers out there? Would it be possible for someone to put one together that noone know what it was going to do until it did it?
How perfectly goddamn delightful it all is, to be sure. - Charles Crumb
Why dont you do it? you Pigfucker.