mirror of https://github.com/raandree/NTFSSecurity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4.2 KiB
4.2 KiB
| status | last-verified | owner | source |
|---|---|---|---|
| current | 2026-10-05 | active-agent | repository evidence |
Progress
Current status
5.0.0-rc2 is ready on eight stacked local branches from the overnight run of
2026-10-04/05; none is pushed. Each is a PR against master, merged in
this order with merge commits: ai/maintenance, ai/defects-a,
ai/defects-b, ai/defects-c, ai/defects-d, ai/decisions-e,
ai/issue-fixes, ai/release-5.0.0-rc2. The tag 5.0.0-rc2 on the last
merge commit then publishes it through CI (Decision 12). master
(e0f5366) carries 5.0.0-rc1, published on 2026-10-04; the stable Gallery
version is still 4.2.6.
Recent milestones
- 2026-10-02 to 2026-10-04: #91 to #97 aligned the docs with the code,
shipped the help file, kept the docs on GitHub, set version 5.0.0, moved
CI and a wiki generated from
Docsto GitHub Actions, and completed the version history (Decisions 6 to 11). - 2026-10-04: #98 (
e0f5366) added releases on a version tag through CI (Decision 12). The tag5.0.0-rc1published to the Gallery and created the GitHub prerelease; the installed module passed the full suite. - 2026-10-05, overnight run (local branches): the 24 code defects of work
package 5 fixed with regression tests, plus what the reviews found: a
failed retry after taking ownership left the owner changed, and
-PassThruwrote objects after a failed change or under-WhatIf. Maintainer decisions D2 to D5 (Decision 13), the issues #3, #4, #17, #74, #86, and #88 fixed, the 37 open issues triaged,Docs/FAQ.md, Dependabot for the actions, and the prerelease labelrc2. One security review per PR; every Major finding fixed. - 2026-10-05, morning: the maintainer accepted the report's
recommendations. #5 (
Get-ChildItem2 -Attributesmatches any listed attribute; an empty value is an error) and #82 (noSizealias) ship in 5.0.0 as breaking changes onai/issue-fixes. Tests at the top branch: Windows PowerShell 423 passed, 26 skipped; PowerShell 7 394 passed, 55 skipped (449).
Stable capabilities
- 36 cmdlets: access (7), audit (5), inheritance (6), owner and security descriptor (4), privileges (3), long-path items (6), links, hash, and disk space (5).
- Works in Windows PowerShell 5.1 and PowerShell 7. In PowerShell 7,
Get-FileHash2lacksRIPEMD160andMACTripleDES, which .NET lacks (onmasterit still fails there for every algorithm). - Pester tests in
Tests\run in$env:TEMPsandboxes throughTests\TestHelpers.psm1; tests that need privileges skip without them and run in CI, whose runners are elevated.
Open work
- The maintainer pushes the eight branches, opens the PRs, merges them in
order, and tags
5.0.0-rc2once CI onmasteris green; then tests rc2. - Release 5.0.0 through CI (Decision 12) after the tests: remove the
label, date
[Unreleased]as[5.0.0], tag5.0.0(steps inDocs/Contributing/05-Releasing.md; CI warns when the changelog date isn't the release day). - Repository settings: the hardening proposed on 2026-10-04 isn't applied yet (checked 2026-10-05); the maintainer applies it before pushing the stack. The details are with the maintainer, not in the repository.
- Open bugs from the triage: #34 and #67 (the write includes owner and
group;
fix/#34swallows every error) for rc3 if a file server to test against is available; #41 (a drive root reads the device object) and #90 (a trailing space in a folder name) after 5.0.0. Enhancements: #22, #49, #68, #77, #87. pwsh7.6.1 crashed three times during test runs on the ARM64 workstation (x64 emulation) with an access violation incoreclr.dllorSystem.Management.Automation.dll, without module frames; not reproducible on demand. Check whether CI on native x64 shows it.- Minor review findings that the PRs list but don't fix, for example
Copy-Item2 -WhatIfreporting a destination conflict as an error, and relative path forms that the*-Item2cmdlets resolve themselves; the maintainer tracks the useful ones as issues. - Optional for the maintainer: delete the AppVeyor project and revoke its
GitHub authorization, restrict wiki editing to collaborators, and ask
Sup3rlativ3to delete the Read the Docs project.