Raimund Andree da41a8e3ee fix(access): end a collection that holds itself and name the typo in the message of a list The check that rejects a list for -AccessType and -AppliesTo opened every level of a collection of one element, so that a collection that holds itself never returned. It opens at most 32 levels now and counts a deeper nesting as a list, and it stops reading a collection after the second element, so that a long or endless sequence is not read to its end. The message names what the caller wrote: the one element of a collection of one element (also when that element is a collection itself), the first ten elements of a longer collection followed by "...", and otherwise the text of the value. Before, a collection of one misspelled name was named by its type. Tests, written first: 28 rows failed on the previous build in all four configurations and none fails now. They cover an array of one misspelled name, a collection nested 40 levels deep for both parameters of both cmdlets, and an array that holds an array of one name, which stays valid. The assertion of the value text expects "The value '<text>'", because the old pattern could also match the name of a type. The comments say that PowerShell combines the numbers of a list bit by bit, which is what it does, and not that it adds them. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>		1 week ago
.github	ci: Bump the github-actions group with 2 updates	2 weeks ago
.memory-bank	docs(memory-bank): record the merge of #128 and the CI of #129 and #130	2 weeks ago
Docs	docs: state the reason for the list rule and the edge cases of the filter exactly	1 week ago
Log	Updated projects to use NuGet packages	9 years ago
NTFSSecurity	fix(access): end a collection that holds itself and name the typo in the message of a list	1 week ago
NTFSSecurityTest	new upload	10 years ago
PrivilegeControl	feat!: prepare version 5.0.0 with a valid module manifest	4 weeks ago
ProcessPrivileges	fix: guard remaining object and cmdlet behavior paths	3 weeks ago
Security2	fix(security2): keep a descriptor without an item usable by the cmdlets that take a security descriptor	1 week ago
TestClient	Updated TestClient project	9 years ago
Tests	fix(access): end a collection that holds itself and name the typo in the message of a list	1 week ago
.gitattributes	Update of AlphaFS to latest version	10 years ago
.gitignore	chore(gitignore): ignore Memory Bank session checkpoints	4 weeks ago
CHANGELOG.md	docs: state the reason for the list rule and the edge cases of the filter exactly	1 week ago
LICENSE	Create LICENSE	8 years ago
NTFSSecurity.sln	Updated projects to use NuGet packages	9 years ago
README.md	docs: announce that NTFSSecurity will be archived	4 weeks ago

README.md

NTFSSecurity

[!IMPORTANT] NTFSSecurity will be archived soon. Please move to WindowsAccessControl, which is also on the PowerShell Gallery: Install-Module -Name WindowsAccessControl.

A PowerShell module for managing the permissions, audit settings, inheritance, and ownership of files and folders on NTFS volumes.

PowerShell offers only Get-Acl and Set-Acl; everything between reading and writing an access control list is up to you. NTFSSecurity closes this gap with cmdlets for everyday tasks, such as permission reports, adding or removing a single permission, repairing inheritance, and taking ownership.

Installation

Install the module from the PowerShell Gallery:

Install-Module -Name NTFSSecurity

You can also download a release from the releases page and install it without the PowerShell Gallery; see Installation.

The module runs on Windows in Windows PowerShell 5.1 and PowerShell 7.

Quick start

# Show the permissions of a folder
Get-NTFSAccess -Path C:\Data

# Give an account the Modify permission on a folder, its subfolders, and files
Add-NTFSAccess -Path C:\Data -Account 'CONTOSO\JohnDoe' -AccessRights Modify

# Remove the explicit permissions of that account again
Get-NTFSAccess -Path C:\Data -Account 'CONTOSO\JohnDoe' -ExcludeInherited |
    Remove-NTFSAccess

# List the explicit permissions in a folder tree, including long paths
Get-ChildItem2 -Path C:\Data -Recurse | Get-NTFSAccess -ExcludeInherited

Documentation

Read the documentation in the wiki, which is generated from the Docs folder, or in the folder itself:

Overview: features, requirements, and the list of cmdlets
Concepts: security descriptors, access rights, inheritance, privileges, long paths, and module settings
Examples: common tasks
Cmdlet reference: one page per cmdlet
Contributor guide

The module author's tutorials from 2014 are still a good introduction, although some cmdlet names have changed since:

Version history

See CHANGELOG.md for changes since version 4.2.6 and the version history for 4.2.6 and earlier releases.

License

NTFSSecurity is licensed under the MIT license.