|
That is completely
moronic to act as if he did not do anything but just hex edit the code and
change the name for example on the .exe . He also like a moron had
the infected drones contact his website (which he is registered to) so that he
can see who has been infected to control them. This means that he had more
than just wanting to change the name of an .exe for example, it shows his
intent. Yes you are right about the 7,000 being exploited anyways, and yes
this kid definitely should not get such harsh treatment, but the sad fact is, he
probably will get all of punishment from what someone else did, he is just a
lame kid who should not of took someone else's code to try and be cool first of
all, and now he is paying the price for trying to be cool. I have had some
many people come up to me and tell me they caught the guy that released the
blaster worm and than I have to yell at them and say, "NO they didn't!
They just caught some kid who made a lame variant using the original
worm." Regardless of what he did or didn't do, he will probably get the
blame of the entire thing, guess this will make worm writers a little more
scared and they will start to watch their steps a little more carefully now and
not have the damn drones contact their own website which is registered to their
name.
-SF
|
Title: Message
- [Full-Disclosure] DCOM/RPC story (Analogy) Kristian Hermansen
- RE: [Full-Disclosure] DCOM/RPC story (Analogy) Steven Fruchter
- RE: [Full-Disclosure] DCOM/RPC story (Analogy) madsaxon
- Re: [Full-Disclosure] DCOM/RPC story (Analogy) Kristian Hermansen
- Re: [Full-Disclosure] DCOM/RPC story (Analogy) ww
- RE: [Full-Disclosure] DCOM/RPC story (Anal... Steven Fruchter
- Re: [Full-Disclosure] DCOM/RPC story (Analogy) Jarmo Joensuu
- Re: [Full-Disclosure] DCOM/RPC story (Analogy) Jennifer Bradley
- Re: [Full-Disclosure] DCOM/RPC story (Analogy) Kristian Hermansen
