Xref: utzoo news.software.b:3324 comp.unix.xenix:8223
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!wugate!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: news.software.b,comp.unix.xenix
Subject: Re: B News' Directory permission problem in /tmp
Message-ID: <1475@crdos1.crd.ge.COM>
Date: 25 Oct 89 19:07:31 GMT
References: <8910220254.AA05389@decwrl.dec.com> <37127@looking.on.ca> <1989Oct24.214243.418@virtech.uucp>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Followup-To: news.software.b
Organization: GE Corp R&D Center
Lines: 21

In article <1989Oct24.214243.418@virtech.uucp>, cpcahil@virtech.uucp (Conor P. Cahill) writes:

|  This is not a "feature" of standard System V Rel 3.2 as released by Interactive,
|  and Bell Tech.  When the poster mentioned it in this group I assumed it was
|  a "feature" of SCO UNIX 3.2.  So don't blame AT&T nor POSIX, just blame SCO.

  Actually how about the user? SCO didn't make up the feature, and
certainly I can't "blame" them for implementing a POSIX feature which
helps me provide security on a system. The user could disable this
feature, it is in the manual. You might lay the blame on the
implementors of news for having an implementation which triggers this
behavior.

  SCO is the only vendor currently shipping this level of security. If
you don't need it that doesn't mean you should "blame" them for it, be
glad you run a system which doesn't need it.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon