1993-07-30 - Re: best way to check for modification of self

Header Data

From: csvcjld@nomvst.lsumc.edu
To: klaus@mail.lds.loral.com
Message Hash: cf4184bffc6c144fa92beb87d9cdb9fa397bba7c2eb39126e6ffa0c33874c451
Message ID: <19930730075157658@nomvst.lsumc.edu>
Reply To: <9307301223.AA15123@mail.lds.loral.com>
UTC Datetime: 1993-07-30 12:57:29 UTC
Raw Date: Fri, 30 Jul 93 05:57:29 PDT

Raw message

From: csvcjld@nomvst.lsumc.edu
Date: Fri, 30 Jul 93 05:57:29 PDT
To: klaus@mail.lds.loral.com
Subject: Re: best way to check for modification of self
In-Reply-To: <9307301223.AA15123@mail.lds.loral.com>
Message-ID: <19930730075157658@nomvst.lsumc.edu>
MIME-Version: 1.0
Content-Type: text/plain


  >I am looking for C src or algorithms that would be useful for a
  >program to check its own integrity and make sure it hasnt been
  >modified.

     Try caware.zip, cvirport.zip, and stealth.zip in /pub/msdos/virus
on oak.oakland.edu.

Thread

• Return to July 1993

• Return to “csvcjld@nomvst.lsumc.edu”
• Return to “klaus@mail.lds.loral.com (Christopher Klaus)”

• Return to “Timothy Newsham <newsham@wiliki.eng.hawaii.edu>”

• 1993-07-30 (Fri, 30 Jul 93 05:24:45 PDT) - best way to check for modification of self - klaus@mail.lds.loral.com (Christopher Klaus)
  • 1993-07-30 (Fri, 30 Jul 93 05:57:29 PDT) - Re: best way to check for modification of self - csvcjld@nomvst.lsumc.edu
  • 1993-07-31 (Fri, 30 Jul 93 20:37:33 PDT) - Re: best way to check for modification of self - Timothy Newsham <newsham@wiliki.eng.hawaii.edu>