Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Date:	Fri, 28 Feb 2003 09:45:17 +0100
From:	Corinna Vinschen <vinschen AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: cygwin=ntsec:[no]strict
Message-ID:	<20030228084517.GH24097@cygbert.vinschen.de>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<20030228032655 DOT GA22913 AT redhat DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 20030227224844 DOT 0080be90 AT incoming DOT verizon DOT net> <20030228041946 DOT GB23158 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20030228041946.GB23158@redhat.com>
User-Agent:	Mutt/1.4i

On Thu, Feb 27, 2003 at 11:19:46PM -0500, Christopher Faylor wrote:
> We have *got* to fix this problem.  I think it's giving cygwin a black
> eye.

Sure but IMHO adding a strict option to ntsec is just band-aiding the
original problem.  I don't think that adding this optin would do
us a great service either.  So, from my point of view it's pretty easy:

Either setup creates file permissions so that the tree is useful
immediately...

...or ntsec must not be the default!

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

- Raw text -