[PATCH 3/4] advapi32: Add DACL inheritance support in SetSecurityInfo
Erich E. Hoover
erich.e.hoover at wine-staging.com
Thu Mar 26 16:12:14 CDT 2015
On Thu, Mar 26, 2015 at 2:59 PM, Erich E. Hoover
<erich.e.hoover at wine-staging.com> wrote:
> On Thu, Mar 26, 2015 at 12:10 PM, Piotr Caban <piotr.caban at gmail.com> wrote:
>> The inheritance doesn't occur when function from ntdll are used for setting
>> DACL. This makes your code inside server incorrect. Also your code is not
>> checking handle permissions correctly. If you try to test it keep in mind
>> that if correct inheritance flags are set in security descriptor control
>> field the permissions will be filled when you right-click on file and
>> display security properties on windows.
> I don’t have the time to write a test at the moment, but I find it
> highly unlikely that MS would implement security descriptors in a
> high-level DLL. If that were the case then an application could
> easily hijack the API in order to permit access to files that would
> otherwise be inaccessible. I would guess that
> UNPROTECTED_DACL_SECURITY_INFORMATION and SE_DACL_AUTO_INHERITED
> probably enter into this somehow.
> Besides that I think we should start implementing stored ACLs first,
> before even thinking about implementing suitable inheritance
> mechanisms. I submitted a bunch of patches for this some time ago,
> but Alexandre wasn’t happy with using extended user attributes to
> store this information. I’m just not sure that it’s useful to
> implement inheritance without storing the ACLs, it’ll certainly fix
> some apps but it will likely break a bunch of others.
Whoops, forgot reply-all - sorry for the duplicate Piotr.
More information about the wine-devel