NTFSSecurity

History

Raimund Andree fdd7a8bfdf fix(effective-access): answer a user who isn't an administrator for this computer On a computer in a domain, Get-NTFSEffectiveAccess wrote "Access is denied" and no result for every user who wasn't an administrator of the computer, also for the default -ServerName localhost and for every other name of this computer. The remote interface of the authorization manager of a computer answers only its administrators and the members of Access Control Assistance Operators, and a computer in a domain offers that interface to every caller. On a computer outside a domain the interface is not reachable, so the cmdlet already used the local authorization manager there, which is why the tests passed on the development host and on the CI runners. For a name of this computer, the cmdlet now uses the local authorization manager when the remote one refuses the user. That manager is the one the name asks for, and it answered correctly in every probe on Windows Server 2019, 2022, and 2025 and on Windows 11: for a standard domain user, a local standard user, and an administrator with a filtered token, for the user's own account, Everyone, the Administrator of the computer, and the Administrator and Domain Users of the domain. For the name of another computer, the denial stays an error, as the cmdlet page and the live test of the delegated account describe. Twenty tests of the suite failed in the basic-user mode on every domain-joined machine of the operating-system matrix, with the published 5.0.0-rc7 code and with the code before this change, and pass with it (Windows Server 2019: basic user 782 and 780 passed, 0 failed, in Windows PowerShell and PowerShell 7). A new live test runs the case as the administrator of the file server, who isn't an administrator of the client. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>		2 days ago
..
AccessCmdlets	feat(access): name the computer in the warning of Get-NTFSEffectiveAccess	3 days ago
AuditCmdlets	fix(audit): write a ReadSecurityError in Get-NTFSOrphanedAudit	3 days ago
InheritanceCmdlets	fix: address the review of the issue fixes	7 days ago
ItemCmdlets	refactor: remove the exception filter that no exception can reach	2 days ago
LinkCmdlets	fix(links): name the items in the errors and continue after an invalid path	3 days ago
MiscCmdlets	fix: pass on what a later command raises, and return every item for -Filter .	2 days ago
OwnerCmdlets	fix: pass on what a later command raises, and return every item for -Filter .	2 days ago
PathCmdlets	fix: write why Test-Path2 returns false for a path that is not valid	4 days ago
Properties	feat!: prepare version 5.0.0 with a valid module manifest	1 week ago
Resources	new upload	10 years ago
SecurityDescriptorCmdlets	fix: pass on what a later command raises, and return every item for -Filter .	2 days ago
SimpleAccessCmdlets	fix: pass on what a later command raises, and return every item for -Filter .	2 days ago
en-US	fix(effective-access): answer a user who isn't an administrator for this computer	2 days ago
BaseCmdlets.cs	docs: correct a code comment and the dot rule of Get-ChildItem2	2 days ago
CodeMembers.cs	new upload	10 years ago
Extensions.cs	new upload	10 years ago
NTFSSecurity.Init.ps1	new upload	10 years ago
NTFSSecurity.csproj	fix(help): ship the generated help file so Get-Help works (#93)	1 week ago
NTFSSecurity.format.ps1xml	fix: honor -Account and -SecurityDescriptor in the derived get cmdlets	7 days ago
NTFSSecurity.psd1	chore(release): prepare 5.0.0-rc7	3 days ago
NTFSSecurity.psm1	Cleanup	8 years ago
NTFSSecurity.types.ps1xml	feat!: remove the Size alias that blocked the import next to other modules	7 days ago
OtherCmdlets.cs	fix: disable the privileges also when the pipeline stops early	4 days ago
packages.config	chore: update the pinned actions with Dependabot and list AlphaFS 2.2.1	1 week ago