search

raandree / NTFSSecurity

Managing permissions with PowerShell is only a bit easier than in VBS or the command line as there are no cmdlets for most day-to-day tasks like getting a permission report or adding permission to an item. PowerShell only offers Get-Acl and Set-Acl but everything in between getting and setting the ACL is missing. This module closes the gap.
MIT License
431 stars 61 forks source link

Inherited ACL is not recognised as inherited #40

Open alexkuc opened 5 years ago

alexkuc commented 5 years ago

Hello!

I am running version 4.2.4 of NTFSSecurity on PSv5 (5.1.17763.134). For some reason, NTFSSecurity is not recognising inherited permissions. I have attached screenshots which show this behaviour:

screenshot 2018-12-11 01 17 31

screenshot 2018-12-11 01 18 03

screenshot 2018-12-11 01 18 49

raandree commented 5 years ago

Effective access is constructed using the explicit and implicit permissions on a file or folder. The inheritance has an impact on the result but the result itself has no inheritance information. If you calculate the effective access using the Windows Explorer, there is no information about inheritance either.

alexkuc commented 5 years ago

I see. It makes sense. In that case, how come, there is InheritedFrom field? Is it because of the used class for that cmdlet?

raandree commented 5 years ago

Right, I am just reusing the same class here to also reuse the same formatter. Is this extremely misleading?

alexkuc commented 5 years ago

I wouldn't say it is extremely misleading. From what I understand in terms of UI, output fields which are empty can cause confusion. I suppose if you could hide InheritedFrom field in this output (as it is not used anyway), it would make it more UI/UX-friendly?