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
Message-ID: <3DB5BA56.A76B6463@ieee.org>
Date: Tue, 22 Oct 2002 16:51:34 -0400
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: Avoiding /etc/passwd and /etc/group scans
References: <3DB416E7 DOT 99E22851 AT ieee DOT org> <20021021162246 DOT GC15828 AT redhat DOT com> <20021022162432 DOT GF514 AT redhat DOT com> <3DB58CBD DOT 87B2BDD8 AT ieee DOT org> <20021022181947 DOT GA4729 AT redhat DOT com> <3DB5A076 DOT ABAFF076 AT ieee DOT org> <20021022191217 DOT GD4828 AT redhat DOT com> <3DB5AB53 DOT B434ED90 AT ieee DOT org> <20021022202004 DOT GA6995 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:
> 
> 
> I guess I have to look at the code.  A file with a .exe extension is
> supposed to be executable by default.  It should even show up as -x.
> 
That's without ntsec. With ntsec Cygwin reads the Windows ACL and 
attempts to translate it to Unix modes.

The executability of a file (ultimately by Windows) shouldn't depend on
ntsec, although the mode displayed by ls -l does.
With ntsec you can chmod 666 a.exe and it won't be executable (even
by clicking on it), although ls -l with nontsec will show x
(that's an item I didn't understand in Jason't recent mail).
 
> 
> Do you have an idea about why a fresh install on a new system would have
> problems?  Is this merely because there is no mkpasswd -d happening?

That's the only reason I see, apart from multi-domain. 

Jason raised another issue:
> My WAG is that /bin is 700 and owned by Administrators which causes
> setup.exe to create .exe files with the same permissions. 
I have not followed setup, so ignore the questions if they are worn out:
- Does setup attempt to control the modes of the files it unpack?
- Do the modes depend on the value of ntsec when setup is run 
  (e.g. inheriting from the directory)?  

Pierre