Date: Sat, 24 Nov 2012 13:25:45 -0800 From: Doug Hardie <bc979@lafn.org> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: I Guess I Don't Understand NFS As Well As I Thought Message-ID: <D5720263-6E1E-40D5-BCEA-7246AAFB9B2C@lafn.org> In-Reply-To: <50B12EC7.6060705@tundraware.com> References: <50B12EC7.6060705@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 November 2012, at 12:32, Tim Daneliuk wrote: > Can someone kindly explain what is going on here: > > Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE > (I don't recall seeing the behavior described below > in V8, but then, I don't think I ever tried it). > > Machine B: Linux Mint Desktop > > - Machine A acts as an NFS server for Machine B. > > - Machine A exports a particular directory like this: > > /usr/foo -maproot=myid -network ... > > > - /usr/foo/bar is owned by root on Machine A and has files therein > owned as root:root with permissions of 600. > > - If I access /usr/foo/bar/file1 from Machine B, I cannot read it > but - and this is the part I don't get - I CAN *rename* it. > > What's going on? Since /foo/bar/ is owned by root and everything > in it is 600 root:root, I would not expect a remote access to allow > things like renaming. Clearly I am missing something here, but I > don't get it. What are the permissions on the directory /usr/foo/bar?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5720263-6E1E-40D5-BCEA-7246AAFB9B2C>