NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/hsv/general/4107

Text File | 1992-12-31 | 1.6 KB | 40 lines

Newsgroups: hsv.general
Subject: Re: Uploaded Viruses
Path: sparky!uunet!spool.mu.edu!sol.ctr.columbia.edu!lambda.msfc.nasa.gov!infonode!ingr!sci34hub!cdthq!gary
From: [e-mail] (Gary Heston)
Message-ID: <[e-mail]>
References: <[e-mail]>
Date: Wed, 30 Dec 92 22:16:44 CST
Organization: Garys' Home for Obsolete Computers
Lines: 29

[e-mail] (Leah Wesolowski) writes:

> Well, lemme reword that.
>  If someone uploads a virus, it can't really infect your system
> unless you "load" the program right? Please explain.

Uploading simply moves a file from one system to another. It may
be an infected file, or it may not--it doesn't matter, uploading
doesn't execute the file.

In order to become active, the infected program must be executed
(run, etc.) so that the viral code can do whatever it's designed
to; infect some other files, infect the boot sector (a *program*
that infects a *boot sector* is called a "dropper"; usually, boot
sector viruses can't spread except via media, and then only when
the system tries to boot from the infected media), check for certain
conditions to be met before doing something (usually a certain date),
or do random/specific damage. If an infected program is not run,
the virus will *not* spread.

This does not mean I consider it a safe practice to keep infected
files on a system. Our viral samples at work (no, we *don't* give
out copies, don't ask) are kept on floppies, in locked cabinets,
clearly marked.

Hope that's not too long-winded or rambling....

Gary Heston, at home....
[e-mail]