bin owns stuff (was: Installing 4.3-Tahoe on a VAX)

[99700000]

In article <8481 at smoke.ARPA> gwyn at brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <21791 at sgi.SGI.COM> vjs at rhyolite.SGI.COM (Vernon Schryver) writes:
>>Is there some risk with making root own everything?
>
>The basic idea is to avoid forcing the system administrator to act under
>UID 0 unless absolutely necessary.  Files owned by "bin" can be updated
>by "bin" rather than "root".

Well as I said when I started the whole thing (and I'm enjoying the
activity level of the subsequent discussion) it is really a philosophical
question rather than a right-or-wrong matter.  I prefer to have root
own everything so I only have to defend one UID against the world
instead of several.  But I can readily appreciate that other system
administrators might prefer to be able to work on the commands without
needing root privileges to do it.  Maybe the goal to shoot for is
having the owner of everything be a define in the top level Makefile
so the installer can do it either way without having to find and edit
all those individual Makefiles.

Now a second related issue is why have all those binaries mode 755 or
worse instead of 711, with 755 to be used only where needed?  Somebody
suggested the umask should be taken into account for installs; but
I'm not sure that is a good idea because you still need 755 for shell
scripts and a few binaries.  But making everything 755 allows a user
to make himself a complete binary-only copy of the system without
getting a license.  Not that I particularly worry about that; I'm
more concerned with trying to make it as hard as possible for the
crackers to find out what's wrong with the programs before I do.
haynes at ucscc.ucsc.edu
haynes at ucscc.bitnet
..ucbvax!ucscc!haynes