Hi Jean-Pierre,
On Wed, 17 Oct 2007, [UTF-8] Jean-Pierre André wrote:
> Szabolcs Szakacsits wrote:
> >
> > 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.
And chkdsk will remove this security descriptor attribute
next time, right?
If Windows does so then we don't need to do it either. I thought
chkdsk removes both the security attribute and the security id then
it replaces them with a third one. But if we do correctly the security
id then it won't be removed, only the obsolote security descriptor.
Do I understand it correctly?
> 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.
Make perfect sense to me.
Thank you Jean-Pierre for checking it out and for the explanation.
Regards,
Szaka
-------------------------------------------------------------------------
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
