[5.4] mode bits changed by close(2)

Daniel O'Connor doconnor at gsoft.com.au
Fri Jan 27 14:28:12 PST 2006

On Saturday 28 January 2006 07:31, dlm-fb at 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.

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060128/a7ca0892/attachment.bin

More information about the freebsd-stable mailing list