Re: A85: Re: Assembly virus


[Prev][Next][Index][Thread]

Re: A85: Re: Assembly virus




If the Virus code is never executed, then it doesn't do anything.
Sometimes they'll target a system file when they are run so they'll be run
more often.

At 06:45 PM 3/10/99 EST, you wrote:
>
>Well how do computer viruses work in that regard?  That is, if you never
>directly access the virus, how does it damage your system?
>
>Justin Bosch
>justin-b@juno.com
>
>On Mon, 08 Mar 1999 21:50:29 -0700 Richard Lewis
><RichardLewis@CedarCity.net> writes:
>>
>>I might be able to make an Usgard specific virus that attaches itself 
>>to
>>the shell and refuses to be removed.  I could make it so it attacks 
>>the
>>menu system and reloads itself every time you use it.  Some slight
>>modifications to the Usgard string would make it impossible to remove. 
>> But
>>it would have to be run from Usgard at least once on every calc...
>>
>>At 09:07 PM 3/8/99 -0600, you wrote:
>>>
>>>I think most of us probably crash our calculators every day anyways 
>>:(.
>>>Certainly you could write a virus.  I would think it would be more 
>>fun to
>>>write one that just made all of the variables grow, little by little. 
>> Or
>>>maybe it did nothing but spread itself across during file transfer.  
>>Once
>>>you crash someone's calc, it would be harder to pass it on to the 
>>next
>>>person.  Anyways, learn some assembly and you can then program your 
>>own
>>>virus.  Good luck (but i don't really think writing most viruses 
>>requires
>>>too many "mad skillz").
>>>
>>>-mike pearce
>>>
>>>-----Original Message-----
>>>From: Matt Cooper <mnemonicdevice@hotmail.com>
>>>To: assembly-85@lists.ticalc.org <assembly-85@lists.ticalc.org>
>>>Date: Monday, March 08, 1999 8:28 PM
>>>Subject: A85: Assembly virus
>>>
>>>
>>>>
>>>>Alright, I know this couldn't possibly work else it would have been 
>>done
>>>>before, but why couldn't someone write code that would use Usgard's 
>>TSR
>>>>calls to attach itself to the system and then wreak havoc with the
>>>>system somehow.  My thought was perhaps have it increment a 32bit
>>>>location, then read a 16bit location which is the less-significant 
>>side
>>>>of the 32bit value.  If that 16bit value = 00 (basically.. the 256th
>>>>time Usgard is loaded) then hang the system.  Or delete variables.  
>>Or
>>>>diddle the first 7 bytes of Usgard so that IT will hang the calc.  
>>Etc.
>>>>
>>>>I don't have the mad skillz to do this, but if I did, I would!
>>>>
>>>>--Matt Cooper
>>>>
>>>>
>>>>______________________________________________________
>>>>Get Your Private, Free Email at http://www.hotmail.com
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>___________________________________________________________________
>You don't need to buy Internet access to use free Internet e-mail.
>Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
>or call Juno at (800) 654-JUNO [654-5866]
>
>
>



Follow-Ups: References: