Rights following extract --no-acls

Comments, questions, bug reports, etc.
Post Reply
ChrisR
Posts: 5
Joined: Fri Nov 20, 2015 2:32 pm

Rights following extract --no-acls

Post by ChrisR »

Hi synchronicity,

At first, thank you for this great tool and all your hard work :)

With the latest version 1.8.3, I have a concern with the rights following wimlib-imagex.exe extract --no-acls

I have a folder (eg D:\Extract_Winre) with owner everyone and full access to everyone
wimlib-imagex.exe extract "D:\Source\Win10_x64\Windows\System32\Recovery\winre.wim" 1 --no-acls --dest-dir="D:\Extract_Winre"
It result with No authorization (at all) has been assigned on D:\Extract_Winre.

I have no problem with wimlib 1.8.2 where I keep original permission to everyone .
synchronicity
Site Admin
Posts: 472
Joined: Sun Aug 02, 2015 10:31 pm

Re: Rights following extract --no-acls

Post by synchronicity »

Hi,

You're correct that there was a change in behavior. To work around an obscure Windows bug, wimlib now removes the DACL from directories being extracted that already existed. This normally makes no difference in the final result, since wimlib will normally set new security descriptors at the end of the extraction anyway. But in your case, the --no-acls option was specified, which caused a directory to be left with no DACL, which grants full access to everyone.

I think this can be considered a bug, and I'll plan to fix it by disabling the DACL removal in --no-acls mode.

Thanks!

- synchronicity
ChrisR
Posts: 5
Joined: Fri Nov 20, 2015 2:32 pm

Re: Rights following extract --no-acls

Post by ChrisR »

Thanks for your quick answer and to confirm :D
For now, no worries, not to change my process, I will keep v1.8.2.
ChrisR
Posts: 5
Joined: Fri Nov 20, 2015 2:32 pm

Re: Rights following extract --no-acls

Post by ChrisR »

I confirm the bug is fixed in wimlib-v1.8.4-BETA2 8-)
Post Reply