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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=BZCTHhu4zithkYZ+ Mlxgs4xJJJJ64/LT1hBRaKvKeYlNqsAIJcyiuCtpCUlFXUGNcTCqz7omgveWgbrM ZTUned1iJJwMkUPRdejNNpeDusFgmbkh+b4wVfbUy6DT2xfPIm7dvlAUj39ALNHK 0qaHJyWMVYmvgwKrl8ajxuGwJDM= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=XWr8/AfXWJ/SGeyZYIX8Pw 2/QfQ=; b=OQD2pqapJxIiNIAFDd122iTdxm+a9ay71QekbWnPCCyK7wjNf98qBh br1xM3zotpXYyxCQoB0Fbo4+89sMcCvj/6rMWuzNeLLFLervOzm891dSbAMifgvw Q6gT66BtVcRBa/tfPN1sBO+tnmoPdckNCNTkQFD58FEzMINvvSRtE= 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=2.3 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,LIKELY_SPAM_BODY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=VERY, colleagues, challenge, H*R:D*ca X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.2 cv=JuuBlIwC c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=N659UExz7-8A:10 a=YunK-HxWpYYIB-Zd7pkA:9 a=pILNOxqGKmIA:10 Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: Challenge: a VERY strange problem with command substitution in bash To: cygwin AT cygwin DOT com References: From: Brian Inglis Message-ID: <435b6eb3-f336-feb6-d326-4204ac50045e@SystematicSw.ab.ca> Date: Mon, 4 Dec 2017 14:40:56 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfHBfj4Vf5lYa/5e3YZAACNQvYg1K0wlIozLXHRrbn6cp/ZePlEZYJSEa/SEcZrale1IOpODUXlOWm3OywThblPrL4r6sI4GfJmbYCe8o+D9AUwdLpnkM aPiBoo6w7PsIqkCJ7As+5UbEqTHMin16u9KrodEgVo9RPAFjeUCiL6VV5jkp/RSmQTfyX+vG9Ff2zg== X-IsSubscribed: yes On 2017-12-04 06:22, David Macek wrote: > On 4. 12. 2017 14:01, Erik Haukjær Andersen wrote: >> Hello >> >> >> I have seen a similar problem on Windows 7, using Cygwin bash version >> 4.4.12(3)-release (x86_64-unknown-cygwin). >> >> After repeating a simplified test on my own host and 6 other >> colleagues, my conclusion is that the cause is found in BeyondTrust >> SecureDesktop, which you also may have installed (I saw you wrote >> something about TrustedInstaller). >> >>   I have raised an internal case with my IT service desk to resolve the >> issue (and see what they can do). > > My understanding is that you're just reporing your findings, not asking for > support here.  Assuming that's the case, the only thing to do here is to add > this to the BLODA. > > I actually can't find any mention of a product nor feature called SecureDesktop, > so unless there are better ideas, let's do only "BeyondTrust". It's a marketing suggestion for referring to the PowerBroker product which manages locking down desktop and server privileges. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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