On Mon, Apr 7, 2008 at 11:21 AM, Scott Lovenberg <[EMAIL PROTECTED]> wrote:
> I think I did this once a couple of years ago using NT style policy and > the firewall policy object. IIRC, I did it all at the file system level; > each computers' SYSTEM service was allowed to write to a text file that it > couldn't read. The files was owned as "root:someGroup" with 720 perms. > This file was in a directory called 'logs' owned "root:someGroup" with 710 > perms. The directory that 'logs' was contained within was owned by > "root:someGroup" with 710 perms and was exported as a hidden share (I think > I used the '$' hidden share trick), which 'someGroup' was allowed to write > to. That's off the top of my head, and it may not be correct, but if you > can mock it up with VMWare and a liveCD, that will at least get the ball > rolling, I hope. I'm fairly sure it worked as advertised, but it never made > it to production, so I didn't document it or anything. > Hello again, I did not understood corrctly: did you made all with fs permissions, what about and what is NT style policy and the firewall policy object? Does this helps me to allow anyone to copy / paste a file into the shares where they have no access? Thanks, Ash. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
