From owner-freebsd-stable Mon Aug 28 9:19:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 0976537B424 for ; Mon, 28 Aug 2000 09:19:39 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 4D2A5E881; Mon, 28 Aug 2000 12:19:33 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id MAA00757; Mon, 28 Aug 2000 12:19:33 -0400 (EDT) (envelope-from khera@kci.kciLink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.37141.115752.674761@onceler.kciLink.com> Date: Mon, 28 Aug 2000 12:19:33 -0400 (EDT) To: David Malone Cc: stable@freebsd.org Subject: Re: NFS client ignores "read-only" attribute on file In-Reply-To: <20000825173313.A54258@walton.maths.tcd.ie> References: <14758.38824.440415.870831@onceler.kciLink.com> <20000825173313.A54258@walton.maths.tcd.ie> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DM" == David Malone writes: Yes, indeed. I just set up another FreeBSD server and the only combination of client/server that lets me ignore read-only attribute is the BSD/OS server with FreeBSD client. Any other combination (of: Linux, FreeBSD, BSD/OS) works as expected. Thanks for your input. DM> On Fri, Aug 25, 2000 at 11:58:32AM -0400, Vivek Khera wrote: >> Example. "kci" is a BSD/OS 4.0.1 server with all applicable patches. >> "onceler" is a FreeBSD 4.1-STABLE (current thru wednesday's version). >> The file system is served from kci to onceler. The FreeBSD system is >> the *only* one that ignores the read-only setting. Linux and other >> BSD/OS systems honor it as expected. DM> The BSD/OS server should not allow you to append to this file, so DM> I would say the problem is with the server. Certainly, from a DM> security point of view it would be the server's responsibility to DM> impliment this. Checking the attributes of the file before writing DM> in the client may even be difficult to get right in the client DM> 'cos the server may do some sort of uid mapping. DM> This problem doesn't seem to occur with a FreeBSD (4.1-STABLE) DM> server. DM> David. DM> Script started on Fri Aug 25 17:26:37 2000 DM> TERM: vt320 DM> 17:26:walton 1% df . DM> Filesystem 1024-blocks Used Avail Capacity Mounted on DM> u2.nfs:/u2 17773026 7401980 8949204 45% /u2 DM> 17:26:walton 2% ls -l hello DM> ls: hello: No such file or directory DM> 17:26:walton 3% touch hello DM> 17:26:walton 4% chmod gu-w hello DM> 17:27:walton 5% ls -l hello DM> -r--r--r-- 1 dwmalone system 0 Aug 25 17:26 hello DM> 17:27:walton 6% echo blah >> hello DM> hello: Permission denied. DM> 17:27:walton 7% ls -l hello DM> -r--r--r-- 1 dwmalone system 0 Aug 25 17:26 hello To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message