From owner-freebsd-questions@FreeBSD.ORG Sat Nov 24 23:28:33 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F7D815E for ; Sat, 24 Nov 2012 23:28:33 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id B17198FC08 for ; Sat, 24 Nov 2012 23:28:32 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.5/8.14.5) with ESMTP id qAONSM5d006245 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 24 Nov 2012 17:28:22 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <50B15813.80202@tundraware.com> Date: Sat, 24 Nov 2012 17:28:19 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: FreeBSD Mailing List Subject: Re: I Guess I Don't Understand NFS As Well As I Thought References: <50B12EC7.6060705@tundraware.com> <50B14C1A.3070605@tundraware.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ozzie.tundraware.com [192.168.0.1]); Sat, 24 Nov 2012 17:28:22 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: qAONSM5d006245 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 23:28:33 -0000 On 11/24/2012 05:13 PM, Doug Hardie wrote: > > On 24 November 2012, at 14:37, Tim Daneliuk wrote: > >> On 11/24/2012 03:25 PM, Doug Hardie wrote: >>> >>> 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? >> >> 775 >> >> >> Let me correct something. The files in that directory are >> owned by root:wheel (not root:root - I got my *nixes >> confused), but they definitely have 600 perms. >> >> On Machine A, user 'myid' is IN the wheel group but I still >> don't see how he's getting permission to rename the file.\ > > Renaming a file does not change the file itself. It updates the directory. Any user in group wheel has the authority to write to the directory (e.g., change a file's name). The directory permissions are rwx for group wheel. You can either try a user on machine B who is not in group wheel or change the directory permissions to 755 on /usr/foo/bar. Then it would work as you expect. > > D'oh ... of course that's it. Thanks. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/