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: Tue, 22 Oct 2002 16:20:04 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Avoiding /etc/passwd and /etc/group scans
Message-ID: <20021022202004.GA6995@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DB5AB53.B434ED90@ieee.org>
User-Agent: Mutt/1.5.1i

On Tue, Oct 22, 2002 at 03:47:31PM -0400, Pierre A. Humblet wrote:
>Christopher Faylor wrote:
>> The same person who chided me was indicating that setup.exe was somehow
>> creating files that were incorrect or that cygwin was unable to execute
>> files with .exe extensions.  I don't really understand what's going on.
>
>The "incorrect" may be from the absent -d 
>I don't understand the non executable .ex, although an "ls -l" that
>does not show the x is understandable.

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.

>> Does it make sense that someone would have to properly generate
>> /etc/passwd and also turn off ntsec in order for things to work again?
>
>There is a possibility in a multi domain environment that a user will deal
>with files owned by a sid that does not appear in the output of a plain
>mkpasswd -d. One would have to do mkpasswd -d specific-domains to have
>correct display in "ls -l" and to chmod such a file (that's one thing I
>know how to make work without running multiple mkpasswd). 
>Turning off ntsec is then an easy  way out.

Hmm.  Interesting.  I don't think this is the scenario we're seeing in
the mailing list, though.  I don't recall people mentioning multiple
domains.

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?

cgf