Repository navigation
ADitor v0.1.1
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 has the same scanner and checks as 0.1.0. What's new is how it's built and tested.
What changed
- Tested on a machine without Python. Before a release is published,
aditor-cli.exeis now run on a clean Windows Server Core machine with no Python, uv or pip installed. That confirms the download really is a single file you can run. - Releases wait for every check. A release is only published after the build, the tests and the clean-machine run all pass.
- New project page at https://alexlinos.github.io/ADitor/, with a sample report you can open in your browser.
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, run this in PowerShell 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. ADitor allows it, but warns every time. - An ordinary domain user account is enough. It doesn't need Domain Admin.
- Treat the report as sensitive. It contains your GPO names, registry values and distinguished names.
Found a security problem? Please report it privately, as described in SECURITY.md.
Full changelog: v0.1.0...v0.1.1