Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 14 Mar 2001 15:46:01 -0500
From: Jason Tishler <Jason DOT Tishler AT dothill DOT com>
To: cygwin <cygwin AT cygwin DOT com>
Subject: Re: Why do DLLs require executable permission with ntsec?
Message-ID: <20010314154601.A86@dothill.com>
Mail-Followup-To: cygwin <cygwin AT cygwin DOT com>
References: <20010313010553 DOT D1084 AT dothill DOT com> <20010313091310 DOT B23263 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010313091310.B23263@cygbert.vinschen.de>; from cygwin@cygwin.com on Tue, Mar 13, 2001 at 09:13:10AM +0100
Organization: Dot Hill Systems Corp.

Corrina,

On Tue, Mar 13, 2001 at 09:13:10AM +0100, Corinna Vinschen wrote:
> On Tue, Mar 13, 2001 at 01:05:53AM -0500, Jason Tishler wrote:
> > In trying to track down a Cygwin Python problem related to ntsec,
> > I first realized that DLLs seem to require executable permission when
> > ntsec is enabled.  Otherwise, the application which is dependent on the
> > DLL will fail to start with the following error dialog:
> > 
> > [snip]
> 
> Sure. This is thanks to Microsoft's straight design of NTFS permissions.
> If you are using NTFS and ntsec is off you will never get this problem
> since the ACL is set to `Everyone may everything'. As soon as you care
> for permissions (from the Windows point of view) you will stumble over
> that... interesting... behaviour. I assume the reasoning behind that is
> that only files with x bit set should be loaded into the text segment.

Thanks for the above cogent description.  I didn't realize that Windows
NT/2000 had anything like the Unix executable bit.  After fiddling around
with Windows Explorer's Properties/Security/Permissions/Special Access...,
I found it.  I (not surprisingly) was able reproduce this behavior directly
using only Windows tools.

It's kind of funny (or sad) that when I work on Windows, some parts of my
brain just stop working.  Luckily they start again, when I get back to
Unix... :,)

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp.               Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason DOT Tishler AT dothill DOT com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple