I was experimenting with security settings this morning on windows, and after changing Mandatory ASLR (Windows Security -> App and Browser Control -> Exploit Protection) to default on, no Cygwin programs that rely on the Cygwin dll would start, stating that a resource was temporarily unavailable and could not fork. Rebasell, bash, you name it crashed and would not start. After some investigation, turning off that setting allows Cygwin to work.
Now the next question: why does this not work? Is this intended behavior or a bug? Having that setting turned on seems like a good idea from a security standpoint, and who knows it may eventually become default. Regards, Alexandria C.
cygcheck.out
Description: Binary data
-- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
