public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@roc.cs.umass.edu>
To: Alexandria Cortez <admin@linuxandria.com>
Cc: cygwin@cygwin.com
Subject: Re: Mandatory ASLR breaks Cygwin - Windows 10
Date: Tue, 25 Aug 2020 10:34:31 -0400	[thread overview]
Message-ID: <4AA035EB-1325-4C1B-B399-28FC9176F203@roc.cs.umass.edu> (raw)
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAALnY9Oyj39Bmm+bZ+AsdEYBAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAACpqdOkYbaoTKteTcuy1wdvAQAAAAA=@linuxandria.com>

It’s intentional; too long to explain in detail on phone, but fork requires each dll to load in the child at the same address as in the parent, and ASLR interferes with achieving that.

Sent from my iPhone

> On Aug 25, 2020, at 10:17 AM, Alexandria Cortez <admin@linuxandria.com> wrote:
> 
> 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>
> --
> 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


  reply	other threads:[~2020-08-25 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 14:16 Alexandria Cortez
2020-08-25 14:34 ` Eliot Moss [this message]
2020-08-25 14:36   ` Alexandria Cortez
2020-08-25 15:13     ` Brian Inglis
2020-08-25 15:25       ` [cygwin] " Jason Pyeron
2020-08-25 15:56         ` Eliot Moss
2020-08-25 21:49           ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AA035EB-1325-4C1B-B399-28FC9176F203@roc.cs.umass.edu \
    --to=moss@roc.cs.umass.edu \
    --cc=admin@linuxandria.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).