X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=CL8jbim2ywBiJLWe
	qWlFZZGj8V5UEQcxym6MASyqzDHUhNS/tyEuQfEciXLosJmqbx9jv92XKCAHid7n
	JwAIbdZSh0dfnHLArtOONQrRSQsFWME0zFvksBUCBEG48C7sOBzd7LxYEyctf67Q
	RZwH3+Oomq+0N8XFF+XaSUJpPJQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=BsRgxhJl8hp8lGagCmlLcM
	+lJkQ=; b=dLNCnYNe5ht+TxILfMGWn+yHjDDxT7BwXsitsn0HmiF4opjtU2Ur1M
	dqIH2aHwqY9UsHBJ8O22dOEGSiIduhohwDIma1P6rzkkw/YOASycMwIuJCctF3xE
	S4oeGYjZzFhEDu/b1Pjuy4o3ZjMPJ3pbh670xibsn1VhLbMobW1FU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtpback.ht-systems.ru
Date:	Fri, 8 Aug 2014 18:41:59 +0400
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<1751963132.20140808184159@yandex.ru>
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
Subject:	Re: Security Settings for directories created in Cygwin (+ executable bit on files)
In-Reply-To:	<20140808104334.GY13601@calimero.vinschen.de>
References:	<86wqajxtm9 DOT fsf AT somewhere DOT org> <20140808104334 DOT GY13601 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Corinna Vinschen!

>> I've noticed that such a behavior happens when I create a new file in
>> a directory that has been made FROM CYGWIN (`mkdir ~/test/', for
>> example).
>> 
>> Indeed, the permissions of CYGWIN-CREATED DIRECTORIES seem very weird:
>> 
>> - "Inherited from"... "None"!

> Perfectly valid.  This has been discussed already years ago.  It's the
> Windows(!) default primary group for users on a standalone machine (not
> domain member machine).  It's the local group with RID 513, called "None"
> on english language systems.

He man that directory security settings are not inherited, when files are
created by Cygwin. Which is explained by a POSIX-adherent behavior of Cygwin.

@Sebastien, if you want Windows behavior (i.e. defer ACL management to OS),
change cygdrive mount flags to noacl.

>> Asking Cygwin to stop playing with the Windows ACL, by mounting my
>> personal directories as "noacl"?  Well, that means I won't be able to
>> use `chmod' anymore,

I don't see a reason to use chmod under Windows at all.

>> for setting a script file as "executable", then.

There's no need. Cygwin automatically detect executables from file contents.

>> And I'll have to use a Windows tool to do so, such as `cacls'.
>> 
>> Is it really so, the integration of Cygwin permissions within Windows?
>> Or do I miss something?

> You're just missing that the integration is one-way.  Non-Cygwin Windows
> executables give a damn for Cygwin settings.  Sorry :}

Also this.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 08.08.2014, <18:37>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -