f.pospischil@telenet-ag.de
2003-Jul-01 10:38 UTC
[Samba] Prevent Samba from setting the execute bit (with inherit ACLs set to YES) ?
Hi there .... Linux (redhat 9.0) does not set the execute-bits for new files, (even with umask set to 777) by default. Why does samba ? When default ACLs are set, samba explicitly sets the mode to 777 for new files and directories, and then somehow corrects them according to the default ACLs. As the default ACLs have to contain an executable bit to allow access to newly created directories, every new file will have this bit set, too. Is it possible to tell samba to treat new files and new directories in different ways to reflect standard unix behavior ? ( i.e. set mode to 666 for files and 777 for dirs) BTW, even setting the force security to 666 does not prevent the file from beeing created with 777 ... We use samba 2.2.8a on redhat 9.0 with XFS as a plattform for cross-system development. Help is very much appreciated ... Frank Pospischil Leiter IT Telenet AG Rhein-Main Darmstadt, Germany Web: http://www.telenet-ag.de
David Morel
2003-Jul-01 10:46 UTC
[Samba] Prevent Samba from setting the execute bit (with inherit ACLs set to YES) ?
Le mar 01/07/2003 ? 12:38, f.pospischil@telenet-ag.de a ?crit :> Hi there .... > > Linux (redhat 9.0) does not set the execute-bits for new files, (even with > umask set to 777) by default. > > Why does samba ? > > When default ACLs are set, samba explicitly sets the mode to 777 for new > files and directories, and then somehow corrects them according to the > default ACLs. > As the default ACLs have to contain an executable bit to allow access to > newly created directories, every new file will have this bit set, too. > > Is it possible to tell samba to treat new files and new directories in > different ways to reflect standard unix behavior ? ( i.e. set mode to 666 > for files and 777 for dirs)in global section directory mode = 0770 create mode = 0660 have you read the manual, or did i not understand your question properly ?> BTW, even setting the force security to 666 does not prevent the file from > beeing created with 777 ... > > We use samba 2.2.8a on redhat 9.0 with XFS as a plattform for cross-system > development. > > Help is very much appreciated ... > > Frank Pospischil > Leiter IT > Telenet AG Rhein-Main > Darmstadt, Germany > Web: http://www.telenet-ag.de-- *********************************************** david.morel@amakuru.net OpenPGP public key: http://www.amakuru.net/dmorel.asc 28192ef126bc871757cb7d97f4a44536 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?Url : http://lists.samba.org/archive/samba/attachments/20030701/bc96fb44/attachment.bin
f.pospischil@telenet-ag.de
2003-Aug-06 09:24 UTC
[Samba] Prevent Samba from setting the execute bit (with inherit ACLs set to YES) ?
Hi there .... Linux (redhat 9.0) does not set the execute-bits for new files, (even with umask set to 777) by default. Why does samba ? When default ACLs are set, samba explicitly sets the mode to 777 for new files and directories, and then somehow corrects them according to the default ACLs. As the default ACLs have to contain an executable bit to allow access to newly created directories, every new file will have this bit set, too. Is it possible to tell samba to treat new files and new directories in different ways to reflect standard unix behavior ? ( i.e. set mode to 666 for files and 777 for dirs) BTW, even setting the force security to 666 does not prevent the file from beeing created with 777 ... We use samba 2.2.8a on redhat 9.0 with XFS as a plattform for cross-system development. Help is very much appreciated ... Frank Pospischil Leiter IT Telenet AG Rhein-Main Darmstadt, Germany Web: http://www.telenet-ag.de From: David Morel <david.morel@amakuru.net> 01.07.2003 12:45 To: f.pospischil@telenet-ag.de cc: Samba Mailing List <samba@lists.samba.org> Subject: Re: [Samba] Prevent Samba from setting the execute bit (with inherit ACLs set to YES) ? ...> have you read the manual, or did i not understand your question properly? Both ist true :-) The question was : Is it possible to create files on a sambaserver (from a Windows Client of course) with no execute bit set, when "inherit ACLs" is set to "yes" ? (Not in theory, I read th manual and I understood that samba forces 777 for new files to ensure ACLs to take effect.) I hoped there would be someone who is also interested in "as close as possible to Unix-Standard-behavior" and provides a patch that creates files with the mode given by "create mask", not hardcoded 777. Thanks for your Question, I hope the topic is clearer now... Frank