Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Info:	This message was accepted for relay by
	smtp02.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace:	UmFuZG9tSVaP1GH9AwSp7JDFbRJP5y5hyV5lYiCdFOJBla3wH5mMv0LmCEOMJ0KJ
Message-ID:	<3F2802B1.3000807@cygwin.com>
Date:	Wed, 30 Jul 2003 13:38:57 -0400
From:	Larry Hall <cygwin-lh AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin and NTFS
References:	<Pine DOT LNX DOT 4 DOT 44 DOT 0307301700450 DOT 13458-100000 AT localhost DOT localdomain>
In-Reply-To:	<Pine.LNX.4.44.0307301700450.13458-100000@localhost.localdomain>

Elfyn McBratney wrote:

> On Wed, 30 Jul 2003, Menon, Girish (MED, WIPRO-GE MED) wrote:
> 
> 
>>Does anybody know of any issues that cygwin 1.3.22 has with NTFS?
>>
>>Here's what happened.
>>
>>So far, I have been using cygwin 1.3.10 on NTFS with no problems.
>>Recently, I upgraded cygwin to 1.3.22 and all of a sudden I am starting
>>to get permission errors with NTFS. I then reloaded by system and
>>configured as FAT32 instead of NTFS. Now everything works fine. No
>>permission problems at all. So I reloaded with NTFS now. Now again, I am
>>getting the permissions problems. 
> 
> 
> I can't remember exactly what version the behaviour changed but, Cygwin went to 
> ntsec off by default (your NTFS bliss) to ntsec on by default. So, adding 
> 'nontsec' to your CYGWIN environment variable should fix that for you.


Right.  This changed for 1.3.13 of the Cygwin package.  Your suggestion,
Elfyn, should work for the current problem but it suggests a
configuration/installation issue at it's heart.  It would be good to
understand this issue better, especially since the workaround compromises
security for openssh at least.  So while using 'nontsec' should solve the
problems with permissions (by disabling them), there is a cost to doing so.



-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -