v2023.12
Mode 4 in the Wild!
This month, the Locksmith team discovered people are actually using Mode 4 (auto-remediation) in the wild. To be honest, we let Mode 4 languish because none of us would trust a fully automated remediation tool... even if we wrote it!
But since it's being used, we should definitely improve it. The new Mode 4 is much more explicit about what the issue is, why it's an issue, and how it will be remediated. Lastly, the Operational Impact is spelled out in plain language and color coded so it's more obvious when a fix may negatively impact operations.

After Locksmith is done fixing stuff on your behalf, you'll get an indicator that it's done instead of just dropping back to the console.
We also resolved some output issues (fewer duplicates), false positives (bitwise math is weird), and cleaned up the scripts used to build the project.
Thank you for using ❤ Locksmith ❤
Improvements:
- Improved Mode 4 output
- Eliminated duplicate RAM
- Improved Manager Approval checks
- Eliminated duplicate ESC4/5 ownership findings
- Tweaked build scripts
Known Issues:
- In ESC4/ESC5 checks, when multiple ACEs exist on a PKS object, all ACEs are displayed instead of Effective Access.
Contributors to this release:
- @SamErde
- @TrimarcJake