fix(win32): try to set ACLs without propagating them #9157
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.




apparently
SetFileSecuritydid not propagate ACLs, unlike its "new" replacementSetSecurityInfo/SetNamedSecurityInfo.SetSecurityInfoshould not perform the propagation if the handle is opened with an access mask value ofMAXIMUM_ALLOWED, so let's give that a try.also removed the restriction on the FILE_WRITE_ATTRIBUTES permission so that
FileSystem::setFileReadOnlyhas an easier time modifying the basic attribute