X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-4.9 required=5.0	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
References: <0105D5C1E0353146B1B222348B0411A20ACC615DB7 AT NIHMLBX02 DOT nih DOT gov>
From: James Coleman <grmrgecko AT gmail DOT com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <0105D5C1E0353146B1B222348B0411A20ACC615DB7@NIHMLBX02.nih.gov>
Date: Tue, 30 Oct 2012 20:09:03 -0500
Message-ID: <7657467952842670611@unknownmsgid>
Subject: Re: cygwin Digest 30 Oct 2012 19:48:59 -0000 Issue 8142
To: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
Cc: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Didn't see Marco's message. Simply adding a id tag to your
documentation and linking to the portion of the document which
contains a solution is a good idea. It'll make it easier for me to
find my solution without learning something I wouldn't need from here
on out.

Thanks Marco, I'll look into it.

On Oct 30, 2012, at 5:54 PM, "Buchbinder, Barry (NIH/NIAID) [E]"
<BBuchbinder AT niaid DOT nih DOT gov> wrote:

> 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