From owner-freebsd-isp Thu Oct 7 2:14:14 1999 Delivered-To: freebsd-isp@freebsd.org Received: from enya.clari.net.au (enya.clari.net.au [203.8.14.116]) by hub.freebsd.org (Postfix) with ESMTP id 9AE34150EC for ; Thu, 7 Oct 1999 02:14:06 -0700 (PDT) (envelope-from danny@freebsd.org) Received: from localhost (danny@localhost) by enya.clari.net.au (8.9.2/8.9.1) with ESMTP id TAA28310 for ; Thu, 7 Oct 1999 19:12:20 +1000 (EST) (envelope-from danny@freebsd.org) X-Authentication-Warning: enya.clari.net.au: danny owned process doing -bs Date: Thu, 7 Oct 1999 19:12:20 +1000 (EST) From: "Daniel O'Callaghan" X-Sender: danny@enya.clari.net.au To: freebsd-isp@freebsd.org Subject: Samba and read-only attribute Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've installed a samba fileserver for a client, and it seems that in scoping the job I failed to discover that the customer makes extensive use of the read-only attribute with the old NT file server, setting RO on files which should not be accidentally changed. The problem lies in the fact that with the old system any user who had rw access to the directory and the files in it could also set the RO attribute. With FreeBSD, only the owner can change the permissions on a file. I've read the samba docs and everywhere it seems to say that samba is never less restrictive than the underlying Unix filesystem. I've e-mailed the samba mailling list and heard nothing. Does anyone have any idea how I can provide the customer with the desired functionality? I'm prepared to hack the samba code and the ufs code if necessary, but I'd prefer not to do that, of course. Please respond quickly. There is urgency in resolving this issue. Thanks, Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message