Hi,

Szabolcs Szakacsits wrote:
> Hi Jean-Pierre,
>
> On Fri, 12 Oct 2007, [ISO-8859-1] Jean-Pierre Andr� wrote:
>   
>> Szabolcs Szakacsits wrote:
>>     
>>> On Thu, 27 Sep 2007, Jean-Pierre ANDRE wrote:
>>>
>>>       
>>>> Note : inheritance and cacheing are not possible on files
>>>> and directories created by standard ntfs-3g.
>>>>         
>>> Do you mean that this is not possible because the $SECURITY_DESCRIPTOR 
>>> attribute was used? 
>>>       
>> Yes.
>>
>> Inheritance is done by copying the security id. Simple and fast.
>>     
>
> Would you please check how Windows handles inheritance if only a 
> $SECURITY_DESCRIPTOR exists? We should behave the same way. Thanks.
>   

When there is a security descriptor Windows XP defines
security ids for files and directories which inherit from
a parent directory. The descriptor for the parent directory
itself remains unchanged.

I have added an equivalent feature for ntfs-3g. There is
a difference though : owner and group should not be
inheritable. But when there is no user mapping, I have
to get them from somewhere, so I copy them from parent
directory. Another possibility would be to use a default,
such as the local administrator.

Of course when user mapping has been defined, owner
and group are those mapped to current process owner
and group.

> Thanks again,
>               Szaka
>
>
>   

Regards

Jean-Pierre




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to