Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!uflorida!gatech!rutgers!njin!limonce From: limonce@pilot.njin.net (Tom Limoncelli) Newsgroups: comp.sys.amiga Subject: Re: IRQ virus Message-ID: Date: 9 Jan 89 00:27:34 GMT References: <27@snll-arpagw.UUCP> Organization: NJ InterCampus Network, New Brunswick, N.J. Lines: 22 In article <27@snll-arpagw.UUCP> paolucci@snll-arpagw.UUCP (Sam Paolucci) writes: > If I understand correctly how the IRQ virus works, I just had a > thought about possible future spread of such viruses which monkey > around with executable files. Why not have the executable generate > its own checksum when the code is generated, and have this checksum > reside in the executable itself. Then when the program is started up > the first thing it does is compute its checksum and it checks the > result with the one stored in the code. If the two match then it > runs, otherwise it doesn't and a message to that effect could be > printed out. > ARPA: paolucci@snll-arpagw.llnl.gov Yeah! In fact, why don't we add a checksum to the boot block? :-) (Sorry, I just had to say it) -Tom -- Tom Limoncelli Drew University Madison NJ 201-408-5389 tlimonce@drunivac.Bitnet limonce@pilot.njin.net "Fences make good neighbors" -Frost "I want an MMU" -Me Standard disclaimer? No, we're still on the dpANS disclaimer.