1993-08-17 - Re: encrypting virus (KOH)

Header Data

From: elee9sf@Menudo.UH.EDU
To: cypherpunks@toad.com
Message Hash: 8050679001363d476eca750253decc21c5021aaac74d46e84ea66038fb6560c8
Message ID: <199308171359.AA04711@Menudo.UH.EDU>
Reply To: <9308170755.AA19760@relay2.geis.com>
UTC Datetime: 1993-08-17 14:00:18 UTC
Raw Date: Tue, 17 Aug 93 07:00:18 PDT

Raw message

From: elee9sf@Menudo.UH.EDU
Date: Tue, 17 Aug 93 07:00:18 PDT
To: cypherpunks@toad.com
Subject: Re: encrypting virus (KOH)
In-Reply-To: <9308170755.AA19760@relay2.geis.com>
Message-ID: <199308171359.AA04711@Menudo.UH.EDU>
MIME-Version: 1.0
Content-Type: text/plain



>         As a matter of fact, when you Stac a floppy, a README file *IS*
> generated, and the stacker.com tsr kindly gives you the 1-800 number you can
> call to order stacker if you received the disk from someone and do not have
> stacker now, but would like to have such a nifty utility on your hard
> drive...
>  

Well maybe things were updated since I bought my copy of Stacker 2.0.
A stacker.log file is created, but it only logs errors during the
screate process.  No mention of compression is made.  If everything
went well, the log file contains no information, except headers and
empty lists.

But then I never stack floppies because I want to be able to use them
wherever I go, something Stacker 2.0 can't do, but Stacker 3.0 does.

I wonder if the author of KOH made this same decision: to insert
decrypting code on the floppy so you aren't tied to using one
computer, or to not "invade" a floppy so you are stuck using one
computer.

/-----------------------------------\
| Karl L. Barrus                    |
| elee9sf@menudo.uh.edu             | <- preferred address
| barrus@tree.egr.uh.edu (NeXTMail) |
\-----------------------------------/





Thread