From owner-freebsd-bugs  Thu Jun 20 17:40:03 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA29891
          for bugs-outgoing; Thu, 20 Jun 1996 17:40:03 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA29879;
          Thu, 20 Jun 1996 17:40:02 -0700 (PDT)
Date: Thu, 20 Jun 1996 17:40:02 -0700 (PDT)
Message-Id: <199606210040.RAA29879@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: kern/1336: Permission for .. in NFS mounts is somewhat non-intuitive 
Reply-To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/1336; it has been noted by GNATS.

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/1336: Permission for .. in NFS mounts is somewhat non-intuitive 
Date: Thu, 20 Jun 1996 17:29:47 -0700

 > This is nothing special to NFS mounts, it's a very generic mount
 > problem.  Try making your /usr 0700 in single-user mode, and go
 > multi-user...
 > 
 > You should never make mount points anything else the 755 (or 555).
 > They are overshadowed with the mount permissions from the newly
 > mounted resource anyway, so the actual permissions of the underlying
 > mountpoint are largely irrelevant as long as they allow all intended
 > access.
 
 But..  That's basically my point - it's *not* overshadowed in the ".."
 case, and this is very counter-intuitive, if not an outright bug.
 
 					Jordan