Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!zodiac!zooks!jordan
From: jordan@zooks.ads.com (Jordan Hayes)
Newsgroups: comp.bugs.4bsd
Subject: Re: Installing 4.3-Tahoe on a VAX
Message-ID: <5432@zodiac.UUCP>
Date: 13 Sep 88 20:52:24 GMT
References: <5415@zodiac.UUCP> <10477@ncc.Nexus.CA>
Sender: news@zodiac.UUCP
Reply-To: jordan@ads.com (Jordan Hayes)
Organization: Advanced Decision Systems, Mt. View, CA (415) 960-7300
Lines: 20

Lyndon Nerenberg <lyndon@ncc.nexus.ca> writes:

	[ a bunch of (lazy) reasons for wanting "bin" to own binaries ]

1) if you can't trust your hackers with an account that has install
   privs on your machine, you can't trust what they are putting there.
   give them a tool to install things, or keep them out of your system
   source.

2) for NFS use rdist.

3) your third answer makes no sense.  if you bnother at all to audit
   your binaries, you should do a thorough job, and not depend on file
   ownership as a sign of "tampering" ...

4) *why* does AT&T do it?

I think my question stands.

/jordan