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=Ya8mOpMUrWBHxg6K
	E/dDEVX0RW/ITJZHVuiafJwBffhPiEqFPQ7gl8ZelpiIqrIss1r46kNDvlVq8KsV
	khaV8tmUA/MLv2VR4YzIsLo3DBkuTU4rau+e5mZIPNvgdyrXO9+uEVSZahI1ntbX
	kRr2Ci65PSIa7i2LM0cSaj8oJOU=
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=g7m93mKCIzOoCr5Gr5MXn6
	ugp6Y=; b=F9mEXrtTm/k0IkGQMmj4Gnd57oC6QlJpZr86a1PrI4M+QmYdrsiYBo
	JMllpKVUm+G6e92fwD5GbrGlye2oboZ3tbjXMSMdO65qZUJAsz8YQ5KBlQqSSk7S
	+6hKGzioy/4bScVNs6tNxBbgDq7QldHEszzIJ/3E+R+KjPhX4Puks=
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-Spam-SWARE-Status:	No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=rice, Rice, prominent, Vince
X-HELO:	hera.deathwyrm.net
Subject:	Re: Re: Setting a bash variable from backtick operator fails
To:	Vince Rice <vrice AT solidrocksystems DOT com>,
	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<8041C6BA-5FCF-4D90-9816-278D29690F41 AT solidrocksystems DOT com>
From:	Numien <numien AT deathwyrm DOT com>
Message-ID:	<d1428b60-117a-d82c-9bb3-ea4c28a4a54c@deathwyrm.com>
Date:	Wed, 28 Feb 2018 17:23:03 -0500
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version:	1.0
In-Reply-To:	<8041C6BA-5FCF-4D90-9816-278D29690F41@solidrocksystems.com>
Received-SPF:
X-AXIGEN-SPF-Result:	Ok
X-AXIGEN-DK-Result:	No records
DomainKey-Status:	no signature
X-AXIGEN-DKIM-Result:	No records
DKIM-Status:	no signature
X-AxigenVirus-Level:	1

On 2018-02-27 03:37 PM, Vince Rice wrote:
>> On Feb 27, 2018, at 2:29 PM, Kaz Kylheku <920-082-4242 AT kylheku DOT com> wrote:
>>
>> On 2018-02-27 09:10, Numien wrote:
>>> Jürgen Wagner nailed it; it was my antivirus, and disabling the
>>> shellcode injection check fixed it.
>> However, this time-wasting pattern of dealing with the issue by end users
>> is not a good way.
>>
>> A better approach would be to identify some common paterns of BLODA interference
>> and code a test which can detect the interference. This should be executed at
>> startup by the Cygwin shell so that a diagnostic can be displayed to the user.
>>
>>  WARNING: Cygwin detected interference from a "dodgy" application
>>  such as anti-virus software. Your Cygwin installation may malfunction.
>>  See http://<URL-to-BLODA-INFO>
> We await your patch, but you might want to search the archives first.
> https://cygwin.com/acronyms/#SHTDI

I would suggest at least putting a prominent link to the BLODA list near
the top of https://cygwin.com/problems.html instead of 3rd from the
bottom in the FAQ.


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

- Raw text -