| delorie.com/archives/browse.cgi | search |
| 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:mime-version:in-reply-to:references:from:date | |
| :message-id:subject:to:content-type:content-transfer-encoding; | |
| q=dns; s=default; b=Fl5HAw9/Abz9xyEfYAHEFwZfFlF1y7M4h51ou1P95uE | |
| aFK6n4VryTbAtSk+n7Jwim2RFlB7chdNH0Yk+lGS17yjFjtW+MFCO50xxuwKAtUh | |
| kasuXVkHqWrjeie/iarx1RbaYUrRugUdDTBjbWaEYcrn3dD+D0ZeqqscEvUyZDug | |
| = | |
| 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:mime-version:in-reply-to:references:from:date | |
| :message-id:subject:to:content-type:content-transfer-encoding; | |
| s=default; bh=olz/IB8Ery5WwKNIFd27wxIoQCI=; b=FQzjapEup2QpCbVRm | |
| lFS2HXglOD1/wKX0o94rRY4Y4/a+DRR3axSYgy6vhh92EquG1m2EHoTKl16oRwOW | |
| qvsqhbgOCAmzxSRQp9C0IyFeOt5Rdu0/3wB+xr4masCFAjQUReQRNebexU87SRC5 | |
| 7oKJu+qzQbh0v8HdxQLoDYKyyI= | |
| 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.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=puzzled, swear, rarely, intrusion |
| X-HELO: | mail-io0-f182.google.com |
| X-Google-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-transfer-encoding; bh=rO+3MP9Jf5kVd7R6UCJDGWFUHHTD+n6tyOOlfuTRDoo=; b=PWotM/t1nnQxMPbUe+JSviEQBAvHrR59+iFpR4H9azLdkf7aN3cWATbDC8pD/UMXFf g4EMHr7KnhLA390ZBoqhb92yjHxCx5AuXMivcYkRsRmFF37JHfccIRlmN2eUIbPMByju QzJ+k9DxWfGMK0LZbPXBAIfGZYVVrHLXPCZ9Fo84xzZwTHS3hdRPwh8rQ+6Ca6lVZiBc PHSFpDf5i4gxhTokrFfM4eWzIEDABqpgu4NfGKhA1BDeTxmqPS8f9cd6zJY7oTZk41FT qOqj56zoTax22a/LLVDTMZ1EV4T8y/hPbLzcVeQ/rNG+bl/t3FUvIO5nY4oM/QQSji72 mQ2g== |
| X-Gm-Message-State: | AIVw111buz9tebAAYaGtyXkJ/N1HX8v1iMpA8q9WqMYB14zzRWGuKqMH 9f+Fck12BnS+/qDbCpPYvX2uF07piA== |
| X-Received: | by 10.107.192.135 with SMTP id q129mr4157419iof.63.1499839632073; Tue, 11 Jul 2017 23:07:12 -0700 (PDT) |
| MIME-Version: | 1.0 |
| In-Reply-To: | <59655e58.d532240a.ae3d8.4253SMTPIN_ADDED_MISSING@mx.google.com> |
| References: | <93b0a4e1-78eb-798e-9946-cd38ab288cce AT wagner DOT is> <59655e58 DOT d532240a DOT ae3d8 DOT 4253SMTPIN_ADDED_MISSING AT mx DOT google DOT com> |
| From: | Wouter van Doorn <wouter AT vandoorn DOT tv> |
| Date: | Wed, 12 Jul 2017 07:06:51 +0100 |
| Message-ID: | <CANZ2p_e3NLaQGFyjXHP3UGjkAiUh6YhfiZYYCRnQ+ecCfMrjxA@mail.gmail.com> |
| Subject: | Re: Challenge: a VERY strange problem with command substitution in bash |
| To: | Richard Beels <rbeels AT yahoo DOT com>, cygwin AT cygwin DOT com |
| X-IsSubscribed: | yes |
| X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id v6C6B5LU003840 |
I bet Comodo is the golden tip. They have introduced whitelisting without telling anyone, and I have had very strange behaviour (strange until that whitelist explained it) too. Including that subshell thing. They call it 'auto-containment'. Just disable that, and done. Wouter On 12 July 2017 at 00:22, Richard Beels via cygwin <cygwin AT cygwin DOT com> wrote: > At 07/11/2017 at 15:12, Shakespearean monkeys danced on Jürgen Wagner's > keyboard and said: >> >> ... >> Using backquotes instead of the command substitution with $(...) does not >> change the results. I could swear this did work in an earlier version of >> Cygwin on my Windows 7 machine. >> >> I tried this to see if the code in the parentheses is executed at all: >> >> $ value="$( date 2> foo | cat )"; echo "$? <$value>" >> >> The file "foo" was not created, i.e., it seems the commands don't really >> get executed. >> >> $ value="$( date && pwd )"; echo "$? <$value>" >> 0 <Tue Jul 11 20:49:09 CEST 2017 >> /home/juergen> >> >> $ value="$( date || pwd )"; echo "$? <$value>" >> 0 <Tue Jul 11 20:32:27 CEST 2017> >> >> both work, so some control structures seem to be permissible... just not a >> pipe. >> >> What is going on? Some misconfiguration? A Cygwin bug? Some interaction >> with something weird in Windows 10? I am at loss to understand what could be >> wrong... and am now most curious whether anybody has an idea what is causing >> this. Does it work/not work in the same way in your Cygwin installation? >> >> I came across this effect because ssh-host-config did not recognize me as >> administrator anymore. It's due to a check for a certain user group that >> uses a command substitution with a pipe. Replacing this with an equivalent >> command works. The original line used "id -G" and then a "grep -Eq" to check >> whether a certain group is on that list. >> >> I am VERY curious now! I've rarely been puzzled that much by such a very >> elementary shell expression (looking back at 34 years of Unix experience). > > > > Hi Jurgen. > > 90% chance it's what is called bloda in these parts. It's in the FAQ on > cygwin.com. I'll go out on a limb and say you might have just > installed/changed your AV/Firewall software. > > And if I want to be super-psychic, can I guess comodo? Because I just > changed to comodo a couple weeks ago and had the same subshell/command > substitution/pipeline errors you're mentioning. > > If so, you need to exclude your cygwin folder from AV scanning. AND... if > the software does whitelisting or host intrusion protection (HIPS) or "run > unknown executables in a container/sandbox" or something similar, you also > need to trust all the executables, too. Or switch to something else that > doesn't trip cygwin's trigger. > > After doing that and a rebaseall, I haven't had a fork error in a week. I > can't wait to run setup and come up with an update process, though... > > Cheers! > > > > -- > 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 > -- 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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |