From owner-freebsd-stable@FreeBSD.ORG Wed Nov 27 12:03:21 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5162B2B7 for ; Wed, 27 Nov 2013 12:03:21 +0000 (UTC) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D1AD42B5C for ; Wed, 27 Nov 2013 12:03:20 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id rARC3BVB001234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Nov 2013 13:03:12 +0100 (CET) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <5295DF79.8060400@omnilan.de> Date: Wed, 27 Nov 2013 13:03:05 +0100 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Feature request: sticky bit inheritance X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig018AA610A2354483A05CDDA9" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 12:03:21 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig018AA610A2354483A05CDDA9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, ever since I took a FreeBSD machine into production, acting as any kind of file server, I have to work arround the problem, that write access to a directory implies unlinking (deleting) directory contents. Never heard any sensible explanation why anybody would ever want that behaviour, but it's been like that for decades and everybody seems to be fine with that!?! Maybe because there's the stick bit, which is a usable workarroun= d. Unfortunately, there's no =E2=80=9Csticky=E2=80=9D equivalent in nfs4acls= =2E More unfortunate, newly created directories don't inherit the sticky bit =E2=80=93 unlike the group settings. And most unfortunate, I'm not able to implement sticky bit inheritance myself :-( Since there's already a kind of inheritance when calling mkdir(1), I guess extendig the inheritance to respect the sticky bit shouldn't be too complex, is it? I'd love to see a sysctl which controls the behaviour, so there's no unexpected behaviour, but the possibillity to make FreeBSDs filsystem-permission-control more real-world-usable. But if a sysctl is noticable more effort than just a kern-conf (compile time) option, I'd also highly appreciate that option! Is there anybody who might want to look into that? Thanks, -Harry --------------enig018AA610A2354483A05CDDA9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlKV338ACgkQLDqVQ9VXb8h0LQCfVUp4T48D9KHk2/ToL9cBemYZ 5xYAn0HAcLTWhEF0tUNigBMKLyzV9U2g =ddOw -----END PGP SIGNATURE----- --------------enig018AA610A2354483A05CDDA9--