DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=H2O4v
	QZQKBl9rbyqti40pBoPM+cRgkLylkYN335WmGO3iGqJdSKHIelwM6QWPLQ7TbJta
	2lNKgSdoWmAuoVQZQVF2Qy3K4uURZ60aQ4nZus8HfMc1XND0M2In7Y2nCmuOw5I6
	SBppYx5PWcuY+DKrCbNrObbTcUAToMAnGlSx4Y=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
References: <7ad0e0d4-438b-33ad-a711-e0b1996fa6f6@gmail.com>	<c1505248-8d03-c0b6-37ca-9c6eed2100e9@cornell.edu>	<c618e65c-ab40-287d-39fb-d9daa9ef858a@gmail.com>	<20180709090332.GC3111@calimero.vinschen.de>	<87e94b8c-13d0-928e-957d-c32b15b8a962@gmail.com>	<20180709123739.GB27673@calimero.vinschen.de>	<fd7e7ce2-84fd-aef3-b54a-0ff76ef8900c@gmail.com>	<CAB8Xom_DX=u0q17ewfRokh_mTcBYMppPZdDLS3UUdaPm5GMV4w@mail.gmail.com>	<20180712133847.GT27673@calimero.vinschen.de>	<c1aa10ad-e685-f232-6719-5c653f747f83@gmail.com>
Date: Sat, 14 Jul 2018 16:50:24 +0200
In-Reply-To: <c1aa10ad-e685-f232-6719-5c653f747f83@gmail.com> (Marco Atzeri's	message of "Thu, 12 Jul 2018 18:35:12 +0200")
Message-ID: <874lh17txr.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Marco Atzeri writes:
> currently I have over 73000000 always busy
> 73C50000-73C51000 /cygdrive/c/Windows/SysWOW64/cryptbase.dll

What type of Windows do you use?  I have Home N for testing at home and
Server 2016 plus a bunch of users w/ Enterprise clients (will get one
myself in a few days) and never seen any such problems.

>> You could reboot the machine until the DLLs are at an adddress you
>> can work with and then never reboot again.  /duck/
>
> Feasible, just time consuming..
> It took a dozen trials before reaching a nice
>
> 71D10000-71D11000 /cygdrive/c/Windows/System32/wow64.dll
>
> the last lottery numbers were:
>
> 5A9B0000-5A9B1000
> 66AB0000-66AB1000
> 53DA0000-53DA1000
> 6A470000-6A471000
> 6DBF0000-6DBF1000
> 5F020000-5F021000
> 680D0000-680D1000
> 52650000-52651000
> 71D10000-71D11000
>
> Now I am stuck to German system and never
> restart. Until next MS patch day...

Are you using one of the preview update channels or did you use one in
the past?  Leading up to 1803 MS has apparently tested some new ASLR
tricks and I don't think they change the settings back to default even
when you are later switching back to a "normal" release version.

Anyway, with 1803 there is a setting now in the security panel somewhere
that forces ASLR to be used even when the PE flags say otherwise.  I
don't know if that can be switched on just for the WoW64 subsystem, but
it would probably be something you can do via group policy (on a Pro or
Enterprise client).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple