Repository navigation
ADitor v0.1.2
ADitor checks your domain's Group Policy and a few directory settings against a catalog of hardening controls, then writes a report you can hand to someone. It only reads; it never changes anything in the directory or SYSVOL.
This release fixes results. Your verdicts may change compared with 0.1.1, and comparing a new scan with an older one in History will say "Different ADitor versions". That's expected: the differences come from these fixes, not from your domain.
Fixed
- A GPO only counts where it applies. Before, a setting counted even if its GPO was unlinked, its link was disabled, or it was linked only to an OU without the machines the check is about. So a domain-controller setting sitting in an unused GPO could show as a pass. Now:
- A setting only counts through an enabled link.
- For domain-controller checks, that link must be on the domain root, the Domain Controllers OU, or a site.
- A GPO with its computer settings disabled counts nowhere.
- A setting that doesn't count is still shown, with a note naming the GPO and why.
- Site links are read, so a GPO linked to an AD site isn't treated as unlinked.
- A pass next to an unreadable GPO is now "unknown". If a GPO that applies couldn't be read, it could be setting a weaker value, so ADitor no longer calls the check a pass.
- Step 1 of a rollout says what it really does. It used to be called "audit mode" that blocks nothing, for every check. That was wrong for NTLMv2 (level 3 already stops old devices that only accept NTLMv1) and for LDAP channel binding. Each check now describes its own first step.
- Kerberos: any AES-only value passes. The domain-controller encryption-types check used to accept only 0x38, so 0x18 (also AES only) failed. Settings that include RC4 or DES still fail.
- Conflicts between different parts of the domain. When GPOs are linked to different places, for example 1 on the domain root and 5 enforced on the Domain Controllers OU, the report now says machines outside the enforced link really get the other value. It used to say they were "likely overridden".
- A plain GPO name in the sample report, in place of the test name it used to show.
Also
- Both executables now carry product name and version details (right-click → Properties → Details).
- The README has a Code signing policy. Releases will be signed through the SignPath Foundation once the project is approved; this release is still unsigned.
Which file do I want?
| File | Use it for |
|---|---|
ADitor.exe |
The desktop app: connect, scan, and compare scans over time. Needs WebView2, which Windows 10 and 11 already have. |
aditor-cli.exe |
The command line, for scheduled tasks, RMM agents and Server Core. |
SHA256SUMS.txt |
Checksums for both. |
Neither needs Python installed. To check a download in PowerShell, run this and compare the result with the line in SHA256SUMS.txt:
(Get-FileHash .\ADitor.exe -Algorithm SHA256).Hash.ToLower()Before you run it
- The executables aren't code-signed yet. Windows SmartScreen will warn you the first time. Choose More info → Run anyway, or build from source.
- Use
ldaps://(port 636). With plainldap://the bind password crosses the network unencrypted. - An ordinary domain user account is enough.
- Treat the report as sensitive. It contains your GPO names, registry values and distinguished names.
Code signing policy: https://github.com/alexlinos/ADitor#code-signing-policy · Security reports: SECURITY.md
Full changelog: v0.1.1...v0.1.2