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:from:subject:reply-to:references:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=R9Tj1FsTv4RFxJVU
	jsio3QxrcRThWkurAtsnsDca45UMlVGtW0m+Z+uZvc0ZZv/nkW6WL2KlsLdTBW4P
	fWMr6XlZM51lD0jUIw2/cY9a9y64Sa+OVAW2O+8CbQNOdYBrYynqxG77rKoXV9L4
	QjdiIQyb1mlcHnrVNbGjyp0zeAg=
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:from:subject:reply-to:references:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=j74h48OZX5QpajonjTeIFx
	B2pKY=; b=VUZ+EBcDnTUevQTjYRzA/6ItI9sHqe6UBI7Cva8eff9QYq6bs0oGcQ
	l3PASVCS4TWjVcFFHbd3NYvb7uazoK4w61HFnnLEu6JJ1LcwG9ZnXDAo0rZyecBp
	9xc9ReGt8Wzbc+ejhURop1/ZNMPUj51EWssz9X4egr/GyBpcTRT0k=
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=2.4 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	eastrmfepo201.cox.net
X-CT-Class:	Clean
X-CT-Score:	0.00
X-CT-Spam:	0
X-Authority-Analysis:	v=2.0 cv=FIzFMZUs c=1 sm=1 a=E2TABC3fJca0I99Ic2bSGA==:17 a=kviXuzpPAAAA:8 a=w_pzkKWiAAAA:8 a=rw-7oMar3DV_RA682S0A:9 a=pILNOxqGKmIA:10 a=E2TABC3fJca0I99Ic2bSGA==:117
X-CM-Score:	0.00
Authentication-Results:	cox.net; auth=pass (CRAM-MD5) smtp.auth=superbiskit AT cox DOT net
From:	David A Cobb <superbiskit AT cox DOT net>
Subject:	Re: Group Permissions on root folders problem (Windows 10 TP build 10061)
Reply-To:	cygwin AT cygwin DOT com
References:	<CAMH9mcFEL3mao+m-DEYM84kC1HOPeSBpZXD+mDf0USobF9oY7g AT mail DOT gmail DOT com> <CAMH9mcFOKjvjiFvvk1ju0ZxBDK28MaktdnYwj5_CjvbgnpVO4A AT mail DOT gmail DOT com> <20150616155843 DOT GE31537 AT calimero DOT vinschen DOT de> <DJzl1r0012qVqVd01Jzm3c>
To:	cygwin AT cygwin DOT com
Message-ID:	<55F1A69D.9050201@cox.net>
Date:	Thu, 10 Sep 2015 11:49:49 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:43.0) Gecko/20100101 Thunderbird/43.0a1
MIME-Version:	1.0
In-Reply-To:	<DJzl1r0012qVqVd01Jzm3c>
X-IsSubscribed:	yes

On 2015-09-05 02:59, Takashi Yano wrote:
> Hi Corinna,
>
> Is there any progress regarding this problem?
>
> I recently encountered the same situation. After some trials,
> I found this problem occurs if the account, on which cygwin
> setup is executed, is a Microsoft account. This does not occur
> if the account is a local account.
> I'm getting an errors saying unknown user win-g71n7drq4r6+cyg_server
> at the point of setting the password, the password expiry and
> assigning permissions.
<SNIP />
>> This is a domain member machine, yes?
>>
>>> *** Info: This script plans to use 'cyg_server'.
>>> *** Info: 'cyg_server' will only be used by registered services.
>>> *** Query: Create new privileged user account
>>> I don't know why this occurs.  As you can see above, it works for me.
<SNIP />
>>>
>>> This is a completely new setup with the Cygwin distro updated to the
>>> latest?  csih 0.9.8-6?  cygwin-2.0.4-1?
>>>
>>>
>>> Corinna
>>>
>>> -- 
>>> Corinna Vinschen                  Please, send mails regarding Cygwin to
>>> Cygwin Maintainer                 cygwin AT cygwin DOT com
>>> Red Hat
Possibly related, or perhaps a totally different bug.

On a Windows-10 host: when I use Cygwin *chown***or *chmod *to make 
permission changes, the next time I access the folder-tree from Windows 
Explorer Security tab, it complains that the Access Control List is 
incorrectly ordered and that will cause undesirable results; happy to 
say, it gives me the chance to re-order the ACL.  The usual undesirable 
result is that an app can create a folder /New/ within /T/ but cannot 
create anything within /T/////New/.

Hypothesis: we are indirectly(?) modifying the ACL but are not observing 
whatever Windows expects for ordering.  I know that Windows enforces 
"*deny*" rules before any "*allow*" rules; I do not know what other 
ordering it observes.  I do know that Windows doesn't really consider 
the "group" property the same way POSIX does, FWIW.



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