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:	Thu, 25 Jul 2002 10:42:00 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Turn on ntsec by default?
Message-ID:	<20020725144200.GA10502@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.3.23.1i

At one time a year or so ago, I turned on ntsec by default in the cygwin
dll.

I'm wondering if it would be worthwhile to do that again.

It's likely that we'd be trading some "Why chmod not work???" questions
for "Why it say permission denied!!!" but I wonder if the benefits would
outweigh the drawbacks.

I know that ntsec only works on NT and NTFS and it would probably make
sense to turn off smbntsec by default if we did this.  But it seems like
this could still be a win.

Any opinions?

cgf

- Raw text -