Date: Sat, 28 Jan 2006 08:57:57 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-stable@freebsd.org Cc: dlm-fb@weaselfish.com Subject: Re: [5.4] mode bits changed by close(2) Message-ID: <200601280858.05260.doconnor@gsoft.com.au> In-Reply-To: <200601272101.k0RL1JB09430@green-dome.village.org> References: <200601272101.k0RL1JB09430@green-dome.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart6432752.d1Zlt9rtjo Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 28 January 2006 07:31, dlm-fb@weaselfish.com wrote: > A demonstration program is included below. I've verified this on a > fairly recently 5.4 client system, with both Linux and FBSD 5.4 NFS > servers. I don't have 6 or -current available to me at the moment. > There's the obvious work-around of doing a chmod() after the close, > but that has security implications. I tested it on a 6.0 server with a -current client.. [inchoate 8:55] /remotehome/darius >~/test ./foo Initial permissions: 0644 After write: 04711 After close: 0711 :( I also get the same result with a loopback NFS mount on -current. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart6432752.d1Zlt9rtjo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQBD2p515ZPcIHs/zowRAnAuAKCSeWzzwmtbmJ2kMIWnUtUMkZA7QgCYorTR KapVV8JGDoTTOp8ayJn/5Q== =KcLZ -----END PGP SIGNATURE----- --nextPart6432752.d1Zlt9rtjo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601280858.05260.doconnor>