Xref: utzoo comp.mail.misc:4003 comp.sys.ibm.pc.misc:1604 comp.mail.uucp:5164 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!billg From: billg@cs.tamu.edu (William Gunshannon) Newsgroups: comp.mail.misc,comp.sys.ibm.pc.misc,comp.mail.uucp Subject: Re: UUPC nuking command.com? (was Re: UUPC 1.08a available) Message-ID: <8158@helios.TAMU.EDU> Date: 11 Sep 90 17:13:21 GMT References: <1990Sep11.115623.6091@mp.cs.niu.edu> <1990Sep11.164626.10348@news.clarkson.edu> Sender: usenet@helios.TAMU.EDU Followup-To: comp.mail.misc Organization: Computer Science Department, Texas A&M University Lines: 30 In article <1990Sep11.164626.10348@news.clarkson.edu> help@kendra.kew.com (Drew Derbyshire - UUPC/extended Help Desk) writes: >From article <1990Sep11.115623.6091@mp.cs.niu.edu>, by rickert@mp.cs.niu.edu (Neil Rickert): >> One question: Some earlier versions of UUPC allowed you to do wonderful >> things such as >> uucp myfile pcnode!/command.com >> >> Mail pcnode!/command.com >> >> Are these wonderful 'features' still available? > >Hmmm ... interesting question. The answer to the question may be yes; >if it is, this is the last release of UUCP that will, because I >promised someone yesterday that I would add a UUCP command to UUPC for >the next release -- and if file transfers are supported, I have to >secure the PC's root directory. (Actually, add a formal permissions file). 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?? bill gunshannon bill@platypus.uofs.edu