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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=I/87ccqGM+UQmV71
	SIMheyuiACYnXw7ujgX8CXXFYRWzHD6bb7cK3am4kJ3CVsGpdNYPSz8Wh4Qd+R1V
	c3Y2QKJSy+IhMFi2c5WUE8hMVgagPoDiQc1ELse9owrCrTN60owSVGxEDusn726O
	QSm6VrEQ4UpRMiNhbfQZRIU0h/g=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=4hLdCNL5mQo7V7Nu9Y7b7s
	9V3Bg=; b=S6txGc4+buLiFq7nG2Jr8CHfqwfsgZSUDdmvl0Cv7WB/Cd2zaCXbWt
	fbW2pvwDOCIlFUPupsv5Im/VMYc9P3mG1BiPQTFQxE+sqWjW5catMRsJ6WbyoNIS
	FwTY3KZPSJVQgg4GhKneUxtlZHJvVQjMP51eN5cmQRII1YQwVpk9E=
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:	=?ISO-8859-1?Q?No, score=4.0 required=5.0 tests=BAYES_20,BODY_8BITS,FREEMAIL_FROM,GARBLED_BODY,GIT_PATCH_2,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=8:=bd, =ef=bf=bd, 8:--, Looked?=
X-HELO:	sonic309-18.consmr.mail.bf2.yahoo.com
Subject:	Re: Window 10 authorization problems
To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca, cygwin AT cygwin DOT com
References:	<373b179e-3c50-2478-3559-f096e7710708 AT bellsouth DOT net> <1df1aa3e-1367-dcac-ed8b-c8e79a92a09e AT SystematicSw DOT ab DOT ca>
From:	Robert McBroom <mcforum AT bellsouth DOT net>
Message-ID:	<56c3c899-0160-f450-e8bd-d2cd1511aaa5@bellsouth.net>
Date:	Thu, 25 Jan 2018 00:22:17 -0500
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version:	1.0
In-Reply-To:	<1df1aa3e-1367-dcac-ed8b-c8e79a92a09e@SystematicSw.ab.ca>
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

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

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.

 �-rw-------� 1 mukx mukx����������� 54 Jan 21 13:37 .serverauth.5628
 �-rw-------� 1 mukx��������� mukx���������� 286 Jan 21 13:37 .Xauthority
 �-rw-------� 1 mukx��������� mukx���������� 764 Jan 21 13:38 
.xsession-errors



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