X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=aa4tte6rWH6IhI5X
	Df6kzMCSXvBUlnKyzlg/YBcT3ftXmfK95oqBNTcqmRoOSZj+LYgc+lT1cNY3/SVd
	wA4eYOtfbIhSlstJhxGoHkhgw5WUne5detI+3H7gt0CvzUxfGf/gISYdjumcpnuH
	ZuJiDlc/P4qEeM64Z2m0CoN10Lg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=nbPQoJw8D1aVN7lnkmid0h
	faT60=; b=w5LSn+r5rwhWDrRuj1GnJvr4plCWliitUlkMKOumD80fy1ULIX77AM
	gcCQc79lRtNMo6hmxNODbcwcJXc+rUrDZ7jQpAY0AoNR0HaC8wRap7t8nMjsXEmx
	JYZqzthNE9s6gpksdF6XHg1nTt26oHFeLrbksrrF84Od8WUjxXDyk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-HELO: mout.kundenserver.de
Subject: Re: mintty fails to start
To: cygwin AT cygwin DOT com
References: <2145564667 DOT 803491 DOT 1484839522957 DOT ref AT mail DOT yahoo DOT com> <2145564667 DOT 803491 DOT 1484839522957 AT mail DOT yahoo DOT com> <1678300909 DOT 1030872 DOT 1484947150343 AT mail DOT yahoo DOT com>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <306e5b52-3098-3832-61a9-e4b88d680609@towo.net>
Date: Fri, 20 Jan 2017 22:35:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <1678300909.1030872.1484947150343@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-UI-Out-Filterresults: notjunk:1;V01:K0:LI7Ve5kYeaE=:C5w+TEh+oAQUzBioZMU+u3 4FvdF0uhuKSo9Sdz1uoUZUK0rLIon/1gWNyI8VYH3QokBLZlsWEzLuqhbzyvQsUkYbQo0r7P8 kmmUHfvzcE+TjTqryliZzGPU6r9jbFnMKttisCAzT1s9CYYBWGhyEQTUYpw42dSv8iF7XcmM4 Iy29hm/n7bqJeQ/uXd40vT9C+ZEI+IEy9kmcA1yNlSG3eEokHghYkYycTTp+fHvIH0DsVS1pE fdqHUA8wUYY1M3SrmaPJnxRpRlEYzpk32XzJJyuKAlaxtHeUen+7jLIxQgvdfgweOHMHINp2W 9Nv6qxgp1aBbh4cWlcQabK09m/hfqicX8kDQMXYNJBZx1cGBl3udWq/46Id7MxajuFdTf/55a I444c7vwSVekA/iwUmwnoZp+YRWd95vwqXAmN6+kcmdpBJ5jsXCErZgMI6ZFft8nXLqxccaQc zXU5WZrCMhV0KL6BGyryTGjMKSskD7fdqsXfJf9DZdLFa6IouVqpSZduTh0qilBQG8tV3veov deygdhY0cJOK+i8+/vXizKmQ/W4ZbvnAEPm5cnreaDClz8WXaISgfYws3Lfrx8QMcp74wbu7u IUlxhy1uim9xo2e+u9QioJej9+rEDMP7vELdoGz1lqaaDEKi6dRPG/iBd5PA4xO+RAshRHmdv PbGJBD2FuFTU/Sum8pv7XNhSer4buBL9irLB0zzTAC8lSS11x8Q8D54UqCMnFxxtvzS5WzYt6 FU5DEt4aGx06IYDx
X-IsSubscribed: yes

Am 20.01.2017 um 22:19 schrieb Emember MemberUS via cygwin:
>      ...
>
>      Suggestion: produce an error message that would help identifying this problem when mintty starts.
>      NOTE: this issue happens only in cygwin, and only when both files are present: /bin/bash.exe and empty /bin/bash.
>      If no bash is present, mintty issues a correct error message.
>
>
>      One interesting test case may be to remove the x bit from the empty bash file, to see that mintty handles invocation errors properly. The issue is that     invocation of an empty file (provided that the x bit is set) is not considered an error in a Linux environment, and thus on cygwin, so the exec system     call does not report an error in the first place.
>      There is nothing that can be done about it, the behaviour is correct.
>      ------
>      Thomas
>
>
> ---------------------------------------------------------
>
> Correction:
> replace <produce an error message> above with <allow logging of exec call(s)>
>
> Current behavior may be correct, but it makes cygwin vulnerable to such hard-to-detect configuration problems.
Please describe precisely what you have in mind. A log output before 
invoking the client program would normally not be desired. You can keep 
mintty from closing with option `-h alw` but you wouldn't see anything now.
Also this issue does not make cygwin vulnerable because on invocation of 
an empty program nothing happens.
------
Thomas

--
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