From owner-freebsd-hackers  Fri Oct 18 20:32:38 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA13960
          for hackers-outgoing; Fri, 18 Oct 1996 20:32:38 -0700 (PDT)
Received: from arvidsjaur (arvidsjaur.anu.edu.au [150.203.160.29])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA13955
          for <freebsd-hackers@FreeBSD.org>; Fri, 18 Oct 1996 20:32:34 -0700 (PDT)
Received: by arvidsjaur.anu.edu.au id <65234-172>; Sat, 19 Oct 1996 13:30:56 +1000
From: Andrew Tridgell <tridge@arvidsjaur.anu.edu.au>
To: terry@lambert.org
CC: julian@whistle.com, Guido.vanRooij@nl.cis.philips.com,
        freebsd-hackers@FreeBSD.org
In-reply-to: <199610190242.TAA02619@phaeton.artisoft.com> (message from Terry
	Lambert on Fri, 18 Oct 1996 19:42:03 -0700 (MST))
Subject: Re: fix for symlinks in /tmp (fwd) FYI
Reply-to: Andrew.Tridgell@anu.edu.au
Message-Id: <96Oct19.133056+1000est.65234-172+1149@arvidsjaur.anu.edu.au>
Date: 	Sat, 19 Oct 1996 13:30:47 +1000
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry wrote:
> Actually, PSIX does mandate sticky bit behaviour in directories.

sure, but does it mandate that the rules for when a user can follow a
symlink? That doesn't sound like a POSIX thing to me, more of a
"tradition" thing. I could easily be wrong :-)
 
Does anyone on the CC list have the relevant POSIX docs handy?

> The historical BSD behavior is group inheritance, actually, totally
> unrelated to the behaviour needed for the bug (I think).

Hmmm, I thought group inheritance was controlled by the setgid bit on
directories? 

Does the t bit really affect group inheritance in BSD? 

I'll have to dig out my NetBSD kernel sources soon :-)

Cheers, Andrew