Forum: Rants Topic: Viruses started by: damien_s_lucifer Posted by damien_s_lucifer on Dec. 16 2000,06:13
fuck 'em.I've had at least 10 machines come in to my store in the last two weeks with the same problem : any program the user tries to start brings up a window that says "Windows is trying to locate WINSVRC.EXE." Half of 'em are warranty repairs, so I'm doing a lot of work fixing a problem and dealing with upset customers because some little insecure bitch with a half-inch dick had to make up for it by showing how 1337 he thinks he is. Virus writers should be tortured in public until they DIE!!!! This message has been edited by damien_s_lucifer on December 16, 2000 at 01:14 AM Posted by Spydir Web on Dec. 16 2000,13:45
I agree virus writing is one of the most bitch ass things a person could do, but only if they release it. I wrote a couple in x86 ASM to test a) my l33t skillz, b) my machine, and c) processor power. I made a couple variations of this one that would ride the processor so hard it would just burn out the whole thing, and one variation could almost start fires in the CPU. I'm not totally sure, cuz I was typing random functions for the code, but I think it just burnt up one transistor or something and routed code out to another... don't ask me, I just coded it . Anyway, I *~*~NEVER~*~* would have aloud that code into anyone but my own hands, for the simple reason of I don't wanna go to jail.So, I guess I'm trying to say that only the people who make viruses and release them are fucknuggets, but if it's for testing then it's ok... I read Intel does shit like that to make sure what I did don't happen... guess I'm just the most k-rad dude around! ------------------ Posted by damien_s_lucifer on Dec. 16 2000,19:20
quote: true. I've written a couple viruses too, but I had code in there to stop them from getting released into the wild. Basically they looked for a signature file on the disk. If it wasn't there, the code stopped. Made 'em easy to stop on MY machine, too. I just deleted the sig file. If you write viruses for experimental purposed, PLEASE include some of firebreak code like that. That way, if they DO accidentally escape into the wild they won't spread. Posted by Michael on Dec. 16 2000,20:04
The problem is, with all the security holes in Microsoft products, and with the degree to which they are integrated with each other, any 12-year-old with a bit of computer knowledge and some free time can program a macro virus / email worm and cause all sorts of damage.Myself, I've never programed any virues or worms, although back when I first learned programming and was just fooling around to see what I could do, I wrote a few programs that would probably have qualified as trojan horses if I had tried to disseminate them... Posted by kuru on Dec. 17 2000,05:59
one time i had this virus.. but the doctor gave me medicine that cleared it up right away.oh wait. wrong kind of virus. i never had that kind, but my sister did. i told her 'the only way to get rid of it is to type fdisk' now she's really mad at me. ------------------ Posted by Bozeman on Dec. 18 2000,05:34
A couple days ago, I got the BleBla worm. Fortunately I had the little bugger wiped out.If you are reading this, and you wrote BleBla, FUCK YOU! Everyone else is ok... Posted by L33T_h4x0r_d00d on Dec. 18 2000,13:32
I wrote a virus too. It consumed all your system resources and it was real unstable. I called it Windows. I think its still going around.
Posted by pengu1nn on Dec. 18 2000,16:28
lol!
Posted by DuSTman on Dec. 18 2000,20:32
The thing that pisses me off about virii is that no-one takes the time to write a really good one. I mean, stuff like melissa is just simple as sin to do, but I kinda miss the artful, assembly programmed, really crafty virii.
|