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:from:content-type:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; q=dns; s=default; b=Hqtq69T/rfOtXxITc1bmu1U8s5EdNNamhtyv+FdIMoq B3SHEcE4vB1Fv8Mwm1WTgachQTW/cTenpkWFuiYxLaGA2LSQpfnxARwupRaNRMGK N0RPdudfv2lMc7YOrhW2witpzIiCwuvITET/TeH0bFSoaUz/E0V4VeMXmgZcIVAI = 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:from:content-type:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; s=default; bh=Iai8cVz4lRnPcguqK6VL7ixoeO8=; b=DBvKPUlK6wiwZ9eHt AxDr+PBrArpk7y7F+JP2403SBRaC1nPz5dKBuRKWjzg8MR+ZGmVLgnKy8bfOjyxK VZd5l7zAMKJLJqbc597ssUtp8rMtcSptfJ97xLmBjh8LjRakbvMingSIFf8Ov4FL 3pqEjdmltu2QtRHa4LzklV6pEs= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=await, antivirus X-HELO: gproxy2-pub.mail.unifiedlayer.com X-Authority-Analysis: v=2.2 cv=M5g9E24s c=1 sm=1 tr=0 a=x/h8IXy5FZdipniTS+KQtQ==:117 a=x/h8IXy5FZdipniTS+KQtQ==:17 a=IkcTkHD0fZMA:10 a=Op4juWPpsa0A:10 a=2KUf1mbJAAAA:8 a=w_pzkKWiAAAA:8 a=Esosv5bBlhezaiQve2QA:9 a=QEXdDO2ut3YA:10 a=LME9DoRMzU6P72L8X6EC:22 a=sRI3_1zDfAgwuvI8zelB:22 From: Vince Rice Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Setting a bash variable from backtick operator fails Date: Tue, 27 Feb 2018 14:37:58 -0600 References: <29d3fea9-89e2-0eab-8bba-486b25fa875b AT deathwyrm DOT com> <574336209 DOT 20180227174741 AT yandex DOT ru> <2562c1b1-e4f7-b76f-20d4-14a05ff9683e AT deathwyrm DOT com> <56fa4a266308c65fef058a94ddc51c85 AT mail DOT kylheku DOT com> To: The Cygwin Mailing List In-Reply-To: <56fa4a266308c65fef058a94ddc51c85@mail.kylheku.com> Message-Id: <8041C6BA-5FCF-4D90-9816-278D29690F41@solidrocksystems.com> X-BWhitelist: no X-Exim-ID: 1eqm0d-0022v7-GB X-Source-Sender: 99-106-192-34.lightspeed.ftwotx.sbcglobal.net ([192.168.1.64]) [99.106.192.34]:50867 X-Source-Auth: vrice AT solidrocksystems DOT com X-Email-Count: 1 X-Source-Cap: c29saWRycjI7c29saWRycjI7Ym94ODY3LmJsdWVob3N0LmNvbQ== X-Local-Domain: yes X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w1RKcFWv016468 > 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:// We await your patch, but you might want to search the archives first. https://cygwin.com/acronyms/#SHTDI -- 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