Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <3DDBD796.6050004@csgsystems.com>
Date: Wed, 20 Nov 2002 19:42:30 +0100
From: Christian Mueller <Christian_Mueller AT csgsystems DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: .rhosts on W2K w/o ntsec
References: <3DDAB456 DOT 4000303 AT csgsystems DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>  > Also, the directories created by Cygwin with ntsec do have
>  > inheritance turned on. In fact that inheritance determines the
>  > ACL of files created by Cygwin when ntsec is off, and also the
>  > ACL created by most Windows applications. Incidentally you
>  > can display these "stupid permissions" with getfacl and change
>  > them with setfacl, so you could add Administrators if needed.
> 
> Hmmm.... it seems as if you mis-interpreted (is this a word?) my 
> problem: The permissions set by Cygwin with "ntsec" are absolutely OK. 
> I'm having problems with permissions set by *native* Windows programs 
> when they create files in my Cygwin home directory....

I just did some tests with CYGWIN=ntsec and it seems as if it's better 
than it used to be a year ago or so. The only thing that doesn't work 
is typing something like "cmd /c xxx.doc" to start the according 
application automatically if the according file is not executable but 
I can write a little script that looks into /proc/registry and figures 
out how to open a file of a given type.

I'll give it a shot, convert all my files to NT security and see how 
it goes. Thanks again.

Cheers,
--Christian


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/