Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!apple!olivea!orc!inews!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.misc
Subject: Re: UUPC nuking command.com? (was Re: UUPC 1.08a available)
Message-ID: <1990Sep12.185335.17658@chinet.chi.il.us>
Date: 12 Sep 90 18:53:35 GMT
References: <1990Sep11.115623.6091@mp.cs.niu.edu> <1990Sep11.164626.10348@news.clarkson.edu> <8158@helios.TAMU.EDU>
Organization: Chinet - Chicago Public Access UNIX
Lines: 32

In article <8158@helios.TAMU.EDU> billg@cs.tamu.edu (William Gunshannon) writes:

>I would think that rather than trying to hack something into MSDOS 
>that it doesn't support/understand (SECURITY), you would be much
>better off to make all file transfers INTO the PC go into a spooling
>directory (uucppublic), and leave the final disposition up to the
>PC user.  There are other files that  you probably don't want over-writen
>other than command.com (BIOS.SYS comes immediately to mind) and rather
>than trying to protect all these obscure files, I think it would be
>much easier to just put them all in one directory and have the user
>sort them out.
>Comments??

Why not just get the files on a diskette instead if you are going to
have to manipulate them manually?
How about simple config file options with PATH-like strings:

READ=
NOREAD=
WRITE=
NOWRITE=
EXECUTE=
NOEXECUTE=

Where the names in the lists could be either directories or files.
It would be useful to have these lists on a per-remote-system basis
but if you accept inbound calls, the determination of the remote
system name must be done bases on a login/password combination since
the uucp handshake name is easy to fake.

Les Mikesell
  les@chinet.chi.il.us