From: Michael Moats <m.moats@3arts.us>
To: cygwin@cygwin.com
Subject: Cygwin terminal fails to start after win update
Date: Wed, 2 Sep 2020 14:32:45 -0500 [thread overview]
Message-ID: <ae289f5e-6670-d55a-607e-f8afb0f3a785@3arts.us> (raw)
Hello. Loaded cygwin a few weeks ago, but after windows 10 update,
mintty term fails to start.
Versions:
cygwin 3.1.6-1
OS Name Microsoft Windows 10 Home
Version 10.0.19041 Build 19041
When problem first noticed:
Error: Could not fork child process: Resource temporarily unavailable (-1).
DLL rebasing may be required; see 'rebaseall / rebase --help'.
(and terminal allows no typing)
When attempt is made to add dll, bash and some other individual
exceptions to firewall ASLR settings, Mintty starts & shell commands
such as echo and pwd will work, but commands from /bin (i.e. ls, ln,
grep, vi, cat, which) return nothing. Maybe more exceptions needed, but
which ones?
To get cygwin working a usual, these gross windows defender firewall
changes were made:
Windows Security
App & browser control
Exploit protection
Force randomization for images (Mandatory ASLR)
Force relocation of images not compiled with /DYNAMICBASE
-> Off by default [Mintty working]
-> On by default [Mintyy not working]
Randomize memory allocations (Bottom-up ASLR)
Randomize locations for virtual memory allocations.
-> Off by default [Mintyy working]
-> On by default [Mintyy not working]
High-entropy ASLR
Increase variability when using Randomize memory allocations
(Bottom-up ASLR)
-> Off by default [Mintty working]
-> On by default [Mintty not working]
When Cyg/Mintty is working with above gross changes:
$ cd /usr
$ ln -s /bin /usr/bin
$ ls -i | grep bin
1125899907459844 bin/
562949954038681 sbin/
$ cd ..
$ ls -i | grep bin
1125899907459844 bin/
562949954038681 sbin/
$ ps -ef | grep -i min
XXXXX 649 1 ? 13:18:14 /usr/bin/mintty
Thanks in advance!!
-- Michael Moats
next reply other threads:[~2020-09-02 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 19:32 Michael Moats [this message]
2020-09-02 22:25 ` Ken Brown
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=ae289f5e-6670-d55a-607e-f8afb0f3a785@3arts.us \
--to=m.moats@3arts.us \
--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).