delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/11/18/17:59:59

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
Message-ID: <003701c28f56$25edb510$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>, "Francis Litterio" <franl AT world DOT std DOT com>
References: <uu1iemqxf DOT fsf AT world DOT std DOT com>
Subject: Re: How do I stop newly-created files from being +x?
Date: Mon, 18 Nov 2002 22:59:28 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Francis Litterio <franl AT world DOT std DOT com> wrote:

> I'm using Cygwin 1.3.15-1 with ntsec on an NTFS filesystem.  I have my
> umask set to "077", and when I create a new file from a Cygwin
> application, it's permissions are "rw-r--r--", which is what I expect.
>
> But if I create a new file from a non-Cygwin application (e.g., copy a
> file using Explorer), Cygwin applications show its permissions as
> "rwxr-xr-x", which is not what I expect.

Sorry, thats the way Windows works. Cygwin can't influence non-Cygwin apps.

> Is there any way to make it so that files created by non-Cygwin
> applications do not appear executable to Cygwin applications?

Turn off ntsec?
Patch Cygwin to use its nontsec 'work out whether it is executable' code
even in ntsec mode?

> I think this is happening because the ACLs on my directory are:
>
> c:\franl MYDOMAIN\litterio:(OI)(CI)F
> MYDOMAIN\Domain Users:(OI)(CI)R
> Everyone:(OI)(CI)R
>
> I think this is happening because the "F" (full control) access is
> marked "(OI)(CI)" (object inherit + container inherit).  I've played
> with cacls.exe to attempt to fix this, but to no avail.

If you do 'fix' this, then you are likely to have problems with .exe and
.dll files being unable to run.


Max.


--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019