From owner-freebsd-security  Sat Apr  1 11:29:59 1995
Return-Path: security-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26078 for security-outgoing; Sat, 1 Apr 1995 11:29:59 -0800
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26072 for <security@FreeBSD.org>; Sat, 1 Apr 1995 11:29:56 -0800
Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id LAA15637; Sat, 1 Apr 1995 11:28:49 -0800
Message-Id: <199504011928.LAA15637@precipice.shockwave.com>
To: Bruce Evans <bde@zeta.org.au>
cc: security@FreeBSD.org
Subject: Re: root owning everything 
In-reply-to: Your message of "Sun, 02 Apr 1995 05:15:53 +1000."
             <199504011915.FAA18492@godzilla.zeta.org.au> 
Date: Sat, 01 Apr 1995 11:28:49 -0800
From: Paul Traina <pst@Shockwave.COM>
Sender: security-owner@FreeBSD.org
Precedence: bulk


  From: Bruce Evans <bde@zeta.org.au>
  Subject: Re: root owning everything
  >Except for setuid files, the majority of files in / and /usr should be owned
  >by root, not bin,  so that I can't nfsmount a volume read-write and su to
  >bin and have a party.
  
  >An alternative would be to map uid bin to nobody the same way root is done.
  
  I don't like files owned by root.  They force me to run as root too much.
  
  The CSRG Makefiles seem to have the same policy as we have (almost
  everything owned by bin).  How is this problem traditionally handled?
  
  Bruce

read only mounts and a lot of praying