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:reply-to:subject:references:from:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=tsWSVfdphsPCpCjT
	8aePC5RfvdZJRpkoQHhho38p1o2wo7FyAQiZUtk+6Q2Lr6SwrmTz/KM+Ka+FM98B
	1da7hVw8e5zcwIjTs2iXGKVdxvYkBLtngA1PyOixhX9/gNmlZJnRyuDwtU4LdDZj
	WEXXm8BLzaA8VwJ0siRfEgmfSvg=
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:reply-to:subject:references:from:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=6nrKDVD/ENUFDJ7mqrc5PW
	khblg=; b=F65xXn3eo2VBuscukfb3PMXXrphzyInEomnoQ8vWYgAsBsPVioA9ZY
	dmVRTMcZLhVtM3xFFISP7FODsu5ORKJLMrDM/NgvnlJOLbjBvfeLe0IoOWnq6/aR
	abwB1/FpG27QWOD7UbmX0RITEJNf5QS762eEJ3O3RTDRVN6vQmyXI=
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.8 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,GARBLED_BODY,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=mailer, rx, Canada, authority
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.2 cv=J/va1EvS c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=N659UExz7-8A:10 a=I7NPD4p0I3RKeXSskUUA:9 a=pILNOxqGKmIA:10 a=x9fSyKahDVsA:10
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: Window 10 authorization problems
References:	<373b179e-3c50-2478-3559-f096e7710708 AT bellsouth DOT net> <1df1aa3e-1367-dcac-ed8b-c8e79a92a09e AT SystematicSw DOT ab DOT ca> <56c3c899-0160-f450-e8bd-d2cd1511aaa5 AT bellsouth DOT net>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
To:	cygwin AT cygwin DOT com
Message-ID:	<9b69d731-033f-a12b-245d-81435f42f770@SystematicSw.ab.ca>
Date:	Thu, 25 Jan 2018 13:32:24 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version:	1.0
In-Reply-To:	<56c3c899-0160-f450-e8bd-d2cd1511aaa5@bellsouth.net>
X-CMAE-Envelope:	MS4wfGp7AjmW3X/4YIJ337kT9bYYzGaX0VTZbr42mzWGhmNPEhTEyxBtXRxBmzQhGOBZj6S2+dLpASRqI8qjzUQ/qDJrUP0vXHijw/BcUyHCymi3Y5jpz2Ar FaxYlXLXuBFKRqbR/oVnBkfsEG/c2S6cbWFtUkJE6eU5d2PfTaDf9KjpMAcFBGbFQm0Kr1/V7EZiog==
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

On 2018-01-24 22:22, Robert McBroom wrote:
> On 01/20/2018 08:39 PM, Brian Inglis wrote:
>> On 2018-01-20 16:35, Robert McBroom wrote:
>>> Troubles through several cygwin releases with getting the files to have the
>>> right permissions when running startwinx from an initial cygwin64 terminal.
>>> Messages follow:
>>> xauth:� /home/mukx/.serverauth.7284 not writable, changes will be ignored
>>> xauth:� /home/mukx/.Xauthority not writable, changes will be ignored
>>> xauth:� timeout in locking authority file /home/mukx/.Xauthority
>>> winInitMultiWindowWM - DISPLAY=:0.0
>>> winMultiWindowXMsgProc - DISPLAY=:0.0
>>> winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
>>> winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
>>> waiting for X server to begin accepting connections .
>>> winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
>>> winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
>>> and so on until the system gives up.
>>> A directory listing gives:
>>> � ----------� 2 mukx��������� mukx������������ 0 Jan 18 18:44 .serverauth.7284-c
>>> � ----------� 2 mukx��������� mukx������������ 0 Jan 18 18:44 .serverauth.7284-l
>>> � ----------� 1 mukx��������� mukx����������� 54 Jan 18 18:44 .Xauthority
>>> � ----------� 2 mukx��������� mukx������������ 0 Jan 18 18:44 .Xauthority-c
>>> � ----------� 2 mukx��������� mukx������������ 0 Jan 18 18:44 .Xauthority-l

You mailer is not setting your charset properly - please fix for readability.

>>> On Window 7 these files are properly read,write for the user.
>> Normally a problem with no default ACls (DACLs) on the directory; use getfacl
>> and icacls to view, and setfacl to set up permissions like:
>>
>> # file: /home/$USER
>> # owner: SYSTEM
>> # group: SYSTEM
>> user::rwx
>> user:$USER:rwx
>> group::---
>> group:Administrators:rwx
>> mask:rwx
>> other:---
>> default:user::rwx
>> default:user:$USER:rwx
>> default:group::---
>> default:group:Administrators:rwx
>> default:mask:rwx
>> default:other:---
>>
>> C:/Users/$USER NT AUTHORITY\SYSTEM:(OI)(CI)(F)
>>              BUILTIN\Administrators:(OI)(CI)(F)
>>              $HOST\$USER:(OI)(CI)(F)
>>
> Thanks Brian.� Made some progress.
> 
> $ getfacl /home/$USER
> # file: /home/mukx
> # owner: mukx
> # group: mukx
> user::rwx
> group::rwx
> other:rwx
> default:user::---
> default:group::---
> default:other:rwx
> 
> The default DACL's look strange with other enabled.� Looked at the root
> 
> $ getfacl /
> # file: /
> # owner: Administrators
> # group: Administrators
> user::rwx
> group::rwx
> other:rwx
> default:user::---
> default:group::---
> default:other:rwx
> 
> Used setacl
> 
> $ getfacl /home/mukx
> # file: /home/mukx
> # owner: mukx
> # group: mukx
> user::rwx
> group::rwx
> other:rwx
> default:user::rwx
> default:group::rwx
> default:other:rwx

Would change that to:
...
 other:r-x
 default:user::rwx
 default:group::rwx
 default:other:r-x

Check icalcs shows similar permissions to getfacl, and use icacls or Windows
Explorer directory Properties/Security to fix permissions, then retry getfacl
and ls -l.
You may have to use Windows Explorer Security to propagate the DACL changes down
your tree.

> startxwin will now run when the initial cygwin64 terminal is started with "run
> as administrator" but not otherwise from the same windows user who is the system
> administrator.

Check your cygwin directory ACLs and DACLs, and apply similar changes as required.

My X start shortcut runs as me:
	C:\usr\local\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec
/usr/bin/startxwin"

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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