X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-4.6 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYGAEFakFCcKEcV/2dsb2JhbABEvyCESYEIgh4BAQEEEihRAQgNCxwCLxMbAQYEAQQBGhqHZAufU4w/kCWLd4VaYQONLIljhHGKN4ML
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>, "Mr. Gecko" <grmrgecko AT gmail DOT com>
Date: Tue, 30 Oct 2012 18:54:53 -0400
Subject: FW: cygwin Digest 30 Oct 2012 19:48:59 -0000 Issue 8142
Message-ID: <0105D5C1E0353146B1B222348B0411A20ACC615DB7@NIHMLBX02.nih.gov>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id qA10PF1U026348

marco atzeri sent the following at Tuesday, October 30, 2012 4:40 PM
>On 10/30/2012 9:05 PM, Mr. Gecko wrote:
>
>> That just explains the security model of Cygwin and windows. I am
>> sure if I read all 5,858 words, then I will be able to fix this
>> issue... However I do not have the time at the moment to do so.
>>
>> I am posting here to get a step by step of how to fix the particular
>> issue rather than having to read a book on how the security works in
>> Cygwin.
>
>methods 1 2 and 3 as presented at the bottom of the document.
>
>> On Oct 30, 2012, at 2:48 PM, Corinna Vinschen wrote:
>>
>>> There was a link in the FAQ entry, which should give you more detailed
>>> information:
>>> http://cygwin.com/cygwin-ug-net/ntsec.html

You should feel lucky that Marco responded without "editorial comment".
If you cannot be bothered to read the documentation, why should anyone
bother to spend the time writing step by step instructions?

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


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