Valid points, though I open for discussion the following logistic issues:
Though the various new policies of various political bodies may have
fluctuated recently, historicly there has been a loophole for which an
attacked entity can respond with due intent to cease the attack via
appropriate me
Follow-up..
[00.00 EST, 04.08.2001; 11.35 EST 03.08.2001 to now (release).]
I just spent 20-30 mins doing a basic tweak of the CodeRed worm.
I need now a known faulty IIS server (or list thereof) preferably with
admin to track the success of the process.
The tweaked code basicly fixes a couple
Continued...
I have found no obvious work on fixes yet...
Resolve: Time to fix this annoyance and be done with it.
Request:
Need a "Simple" set of *instructions* to "paste" a line to apache/etc
server control settings so that other individuals who are running an
apache/etc server may cease "a
At 06:03 PM 8/3/2001 -0400, Wilfred L. Guerin wrote:
>Moreso, if noone is competant to have yet done this, can anyone provide an
>EXTREMELY stable high-load capacity box which can accept reporting of
>infected hosts? -- This would be highly useful in the target analysis of
>the worm's progress...
Greetings all...
I ask a simple and profoundly obvious question...
With eeye and others releaseing codeRed src almost a month ago, has anyone
bothered to modify the worm and bother distributing (by force) the file
checked by the current worm which will suppress its operation?
This is such an o
