Hi Szaka, Hmm, I may have been unclear, so I try again.
> Message du 18/10/07 15:40 > De : "Szabolcs Szakacsits" <[EMAIL PROTECTED]> > A : "Jean-Pierre André" <[EMAIL PROTECTED]> > Copie à : [EMAIL PROTECTED] > Objet : Re: [ntfs-3g-devel] New permission handling version available > > > 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? Not at all. In this scenario there is no duplicate (security attribute and security id). > > 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? > In this inheritance scenario, we have a parent directory, (assume its name is parent), which is old-fashioned, with a security descriptor and no security id. Then, under a recent Windows (or the future ntfs-3g in a special inheritance mode which deviates from Linux traditions), we create a child directory as a subdir of parent. In this situation, the child directory will receive an id designating a descriptor which derives from its parent's, while the descriptor of the parent remains old-fashioned. The parent has only a security attribute The child has an id and a security descriptor in $Secure. None has a duplicate descriptor, and nobody (to my current knowledge) will remove or convert the old-fashioned descriptor from the parent. Please note : in my implementation, every time a file or directory is created in an old-fashioned directory, the process of computing an inherited id is repeated up to finding out, a similar descriptor is already available and its id can be reused. This is due to the fact I do not keep track of files, I only cache their security id if the have one, but in this situation the parent directory has none. 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
