-> SS> checking routines but I did do something similar years ago that would
-> SS> detect any changes made to the main executable (whether virus related
-> Note that your method will only detect changes from non-stealth viruses...
Yes but again, note the context in which I was referring to it.
Someone had posted a message referring to a crude form of virus protection
that they had employed using the exe itself for verification. They had asked
if anyone else had done something similar. Obviously, IMO, my old CRC32
routine _did_ do something similar and so I mentioned it.
I didn't at any point say that my method was any masterful way of
protecting against viruses. Simply from any change to the main exe that
ould
possibly be corruption of the file itself and if the exe did run it may run
with adverse results.
/---------------------------------------------------------------------------\
|Stephen E. Shoesmith -- AKA Lone Wierdo |
|SysOp, MetroPlex Communications - Free Access To Information - 401.739.8118|
|Email: sysop@mtrplx.com or lone_wierdo@ids.net Fidonet: 1:323/1212 |
|Send mail to sspublickey@mtrplx.com for my public PGP key. |
\---------------------------------------------------------------------------/
--- PCBoard (R) v15.23/2
---------------
* Origin: MetroPlex - Warwick, RI - 401.739.8118 (1:323/1212)
|