Xref: utzoo comp.sys.att:6091 comp.mail.uucp:2986
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!faline!thumper!ulysses!sfsup!aeh
From: aeh@sfsup.UUCP (+Herzog A.)
Newsgroups: comp.sys.att,comp.mail.uucp
Subject: Re: UUCP error message
Summary: caution with Permissions
Message-ID: <5115@sfsup.UUCP>
Date: 11 Apr 89 20:34:10 GMT
References: <89096.10:22:17.378274UH2@PSUVM> <659@mccc.UUCP>
Organization: AT&T-BL, Summit N.J. USA 07901
Lines: 18

In article <659@mccc.UUCP>, pjh@mccc.UUCP (Pete Holsberg) writes:
> In article <89096.10:22:17.378274UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes:

Most of the information (from various sources) is on target, but ...

> 	2) Again in the Permissions file, the READ and WRITE parameters
> are not set correctly.  They should at least be:
> 		READ=/usr/spool,WRITE=/usr/spool

DON'T DO IT! Unless of course you want to open up everything writable
by uucp under /usr/spool to persons unknown from remote machines: like
/usr/spool/cron, /usr/spool/uucp [also known as "giving away the shop"].
Make them /usr/spool/uucppublic, and you're OK.

> scott barman
> gatech!dtscp1!scott

Artie