From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 43333 invoked by alias); 3 Mar 2020 04:26:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 43326 invoked by uid 89); 3 Mar 2020 04:26:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=explorer, Explorer, Panel, reveals X-HELO: mail-ed1-f48.google.com Received: from mail-ed1-f48.google.com (HELO mail-ed1-f48.google.com) (209.85.208.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 03 Mar 2020 04:26:13 +0000 Received: by mail-ed1-f48.google.com with SMTP id t7so2632279edr.4 for ; Mon, 02 Mar 2020 20:26:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=3PTczxCC/lEt3em8bFQN6dJ7sikIsbaAEXHfa0s8GH4=; b=HOsDPPelrHUJH/nKlF8F48jxxIykwBmwtYAO2j/H1pddiRfVp6i66WpVoIHcKOEVT9 4TaAQPzkgodgGt5mQK22zcarPAskhLcZdO5YpSEPEiuTeMTO2rfbti+DSc8+lr0ffXxL e8PEZNquXRiUKZ6Bd4V4R6Kawl5tcb2uoVzuZGqo+qsWTnQQSWuJwkE+GWRBqLSWHFUG shL5966eVioR+EDK51sN2ZYG/fA/dyQCCUJRsqTD/7p49cXuBPiJonfpNebYCkjvf77O LpQPhXsWlB0fWJv40E4aOFdl+SQsvGl8HPRCgjFxRFApMrkzDv6xpnWStm/pnON0JE1C voCg== MIME-Version: 1.0 From: John Selbie Date: Tue, 03 Mar 2020 04:26:00 -0000 Message-ID: Subject: ASLR revisited To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-03/txt/msg00030.txt For my open source project, I publish source code for Unix written in C++. And as a convenience, I publish Win32 binaries compiled with Cygwin's g++ build. I bundled the compiled EXE along with the dependent Cygwin DLLs (cygcrypto, cyggcc, cycstdc++, cygwin1, and cygz.dll). Someone rang me up today and said, "We're about to go live with your pre-compiled binaries for Windows, but our compliance testing detected your code isn't using ASLR (Address Space Layout Randomization). Can you fix?" A quick internet search reveals that Cygwin has a compatibility issue with ASRL. Process Explorer from sysinternals.com reveals that the process runs without ASLR. I tried using the Windows 10 Exploit Protection Panel - and specifying an exception for this executable to have mandatory ASLR. That results in the code no longer running. Although the alternate option of "Botton-up ASLR" did allow the code to run, but Process Explorer still doesn't show it running with ASLR. Is there a workaround for allowing Cygwin code to have ASLR? I don't need the fork() function. Thanks, jrs -- 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