Date: Sun, 21 Jan 2001 23:10:24 -0800 (PST) From: Doug White <dwhite@resnet.uoregon.edu> To: Dave Walton <walton@onlinemusic.com> Cc: freebsd-fs@FreeBSD.ORG Subject: Re: suiddir and samba Message-ID: <Pine.BSF.4.21.0101212304440.55271-100000@resnet.uoregon.edu> In-Reply-To: <3A689FFE.16050.192CED5@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Jan 2001, Dave Walton wrote:
> On 19 Jan 2001, at 19:29, Doug White wrote:
>
> > Use samba's 'inherit permissions' option instead. (or something like that,
> > I don't have the man page handy)
>
> I've got "inherit permissions = yes", so the read/write bits are
> inherited properly, but as it says in the samba docs:
>
> "Note that the setuid bit is *never* set via inheritance (the code
> explicitly prohibits this)."
>
> So samba won't set that bit, even with inheritance turned on. But
> as I understand it, suiddir should cause the inheritance to happen
> at the filesystem level. So how come it's not getting set when
> samba creates a directory?
No, turn off suiddir and turn on inherit perms. They are mutually
exclusive.
Also Samba changes the mode on new directories and files according to the
'[force] {directory,file} mode' options. Read the smb.conf manpage about
inherit perms and directory mode and it should clear things up. This
essentially makes suiddir useless unless you force samba to set the suid
bit on created directories. And as I've said, if you're using 'inherit
perms' you don't need suiddir.
At my last job I did a combination of inherit and perm overriding for a
large public file store (win98 sucks -- couldn't they have put a proper
permissions browser on it?).
Doug White | FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu | www.FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101212304440.55271-100000>