If you'd like to see the machinations of a psychopathic personality and
the senseless drivel it produces when arguing with its superiors while
it desperately tries to pretend it knows what it is talking about, read
this page.

http://groups.google.com/group/alt.c...0c73413bdbc007

or

http://preview.tinyurl.com/2ajsneo

It's really funny when you remember this asshole writes his virus ****
in BASIC.

Dave U. Random <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> If you'd like to see the machinations of a psychopathic personality
> and the senseless drivel it produces when arguing with its superiors
> while it desperately tries to pretend it knows what it is talking
> about, read this page.
>
> http://groups.google.com/group/alt.c...ad/thread/d42f
> c252bdec427f/d70c73413bdbc007?hl=en&q=group:*.*+author:martin+authorv
> erton#d70c73413bdbc007
>
> or
>
> http://preview.tinyurl.com/2ajsneo
>
> It's really funny when you remember this asshole writes his virus ****
> in BASIC.

Asic v5 actually; with assembler. You should also post this, for
fairness: http://www.pcreview.co.uk/forums/thread-2000985.php

I believe Krile source code could still be found online if you looked for
it; but I seriously doubt, regardless of language it's written in, you'd
have a clue what you were looking at.

Here's a nice little snippit from the Zvi Netiv scenario. He's not some
well respected AV researcher, like you've tried to imply.


File infectors given free rein
Two integrity checkers are provided with Invircible to handle file
infectors: the Dos IVB and the Windows IVB32. When run, the integrity
checkers compare files to 66-byte 'snapshot' signature files said to
contain all the information necessary to restore them. These 'snapshots'
can be renamed and stored off-line, but they can be deleted without any
reaction from IVB/IVB32.

To see whether Invircible could detect any virus, prevent its
propagation and restore the infected files as promised, I used the KRiLE
virus. KRiLE attacks executables in the PATH variable, encrypting the
first 5,696 bytes of it. Because Invircible's lack of memory resident
protection, KRiLE was able to infect as many files it liked. These
included the Invircible Dos programs, unfortunately. The Dos and Windows
integrity checkers showed that some executables had grown by 5696 bytes,
and gave me the option of restoring them. Both programs claimed success,
but executing the restored files showed that they didn't work.


--
Are you a former BBSer? Want to go back in time to the old days of
ANSI and Renegade? Fire up telnet and go here then: ttb.slyip.com

+1

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
http://www.microsoft.com/protect

"Dustin Cook" <(E-Mail Removed)> wrote in message
news:Xns9D8C8EB0E2537HHI2948AJD832@69.16.185.250...
> Dave U. Random <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):
>
>> If you'd like to see the machinations of a psychopathic personality
>> and the senseless drivel it produces when arguing with its superiors
>> while it desperately tries to pretend it knows what it is talking
>> about, read this page.
>>
>> http://groups.google.com/group/alt.c...ad/thread/d42f
>> c252bdec427f/d70c73413bdbc007?hl=en&q=group:*.*+author:martin+authorv
>> erton#d70c73413bdbc007
>>
>> or
>>
>> http://preview.tinyurl.com/2ajsneo
>>
>> It's really funny when you remember this asshole writes his virus ****
>> in BASIC.
>
> Asic v5 actually; with assembler. You should also post this, for
> fairness: http://www.pcreview.co.uk/forums/thread-2000985.php
>
> I believe Krile source code could still be found online if you looked for
> it; but I seriously doubt, regardless of language it's written in, you'd
> have a clue what you were looking at.
>
> Here's a nice little snippit from the Zvi Netiv scenario. He's not some
> well respected AV researcher, like you've tried to imply.
>
>
> File infectors given free rein
> Two integrity checkers are provided with Invircible to handle file
> infectors: the Dos IVB and the Windows IVB32. When run, the integrity
> checkers compare files to 66-byte 'snapshot' signature files said to
> contain all the information necessary to restore them. These 'snapshots'
> can be renamed and stored off-line, but they can be deleted without any
> reaction from IVB/IVB32.
>
> To see whether Invircible could detect any virus, prevent its
> propagation and restore the infected files as promised, I used the KRiLE
> virus. KRiLE attacks executables in the PATH variable, encrypting the
> first 5,696 bytes of it. Because Invircible's lack of memory resident
> protection, KRiLE was able to infect as many files it liked. These
> included the Invircible Dos programs, unfortunately. The Dos and Windows
> integrity checkers showed that some executables had grown by 5696 bytes,
> and gave me the option of restoring them. Both programs claimed success,
> but executing the restored files showed that they didn't work.
>
>
> --
> Are you a former BBSer? Want to go back in time to the old days of
> ANSI and Renegade? Fire up telnet and go here then: ttb.slyip.com
>

"Peter Foldes" <(E-Mail Removed)> wrote in message
news:hu8vuk$qje$(E-Mail Removed)...
> +1

Are you agreeing that *you* write viruses too, Peter Foads?