(Suggestion) Automate adding necessary ASLR exclusions

[magic-spearmint]

Most binaries from the Cygwin project tend to not play nice with Windows' ASLR exploit mitigation features which are enabled system-wide by default. The usual symptom is that they'll immediately and - most importantly - silently fail to run.

Disabling mandatory and bottom-up ASLR for specific executables can be automated using PowerShell's Set-ProcessMitigation command/cmdlet. Windows 10 Home and Pro have PowerShell 5.x (which has the aforementioned cmdlet) installed and enabled by default.

If wanted, I would be more than willing to adapt an existing small PS script I've written for inclusion with WSLtty. I only need to adjust it so that the code is formalized and abides by strict mode, is triggerable by an installer/external process, and supports checking for, creating, and removing necessary overrides on end users' systems.

[Biswa96]

Would you like to provide some background? For example,

• what issue are you trying to solve?
• how to reproduce the issue?
• should wsltty installer modify the process mitigation settings instead of user?
• wouldn't that backfire to wsltty and antivirus programs will start to flag wsltty more often?

[mintty]

Related to #6 and #239.
Would global disabling also be required as described in #6 (comment) ?
If so, would installation work for a non-admin user?

[mintty]

What's the command to adjust the property properly?

[mintty]

Closing as duplicate and missing prospect of a remedy.