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:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=rF9M
	oGIsqi85lu/qTTTy85689w24l93Qze/WS7AnG6l1CkoHmh0sVv7JmcZrbdl003u3
	PLmCNuG+4iqbEweYxwFfDAaNhy0YwbglxK8seIGagpnKGkFZZLMCnmENT3cvjp8c
	rPAr6g6D1qAyfqtB1BTtxwwML7Kwi9MhO7V8sfo=
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:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=go0/Kyn4do
	XQzbeR0+yZcHWlshM=; b=PoOMvIEk43U2VMA9TPVzmawL7ouf8pcneKVXmBPdNL
	E1vxAJ8V21H6MYCpachY+3bE2e0H/1czGKgBq11piSCWp16SzFfhPnwrDvj3dVDR
	GTfzcPUHV2HMivzDUmVYnhWC+ZUf9lXDxtS7bQqyauTVsySEve52v+Hjp9LEsD1y
	4=
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.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=AUTHORITY, deny, intelligently, SX
X-HELO: earth.ccil.org
Date: Thu, 14 Apr 2016 20:50:47 -0400
From: John Cowan <cowan AT mercury DOT ccil DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Conflict between Cygwin 1.7 and Ubuntu for Windows 14316
Message-ID: <20160415005047.GE29184@mercury.ccil.org>
References: <20160413052257 DOT GB28803 AT mercury DOT ccil DOT org> <CA+Fg1xY46ANusM1MeZozkQ1u0+AHwd=vJDoWo7867az3wxPNBQ AT mail DOT gmail DOT com> <CACmJb3yHO_VhiDoyn33d+7R_rq8Bqco6VMuTdG622Bu2u52fHA AT mail DOT gmail DOT com> <20160413131128 DOT GA3162 AT mercury DOT ccil DOT org> <570E4B45 DOT 7000201 AT cs DOT umass DOT edu> <20160413154351 DOT GF32092 AT mercury DOT ccil DOT org> <CA+Fg1xY+a-PJt7JNawvcWCqOz6GPz1PnivxzQbH4ntzXeMjhyQ AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+Fg1xY+a-PJt7JNawvcWCqOz6GPz1PnivxzQbH4ntzXeMjhyQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-IsSubscribed: yes

Gerrit Haase scripsit:

> Seems to be a permission issue, can you provide the output of:
> 
> icacls file1
> icacls file2

Here they are:

cowan AT large-skunk ~
$ icacls file1
file1 NULL SID:(DENY)(Rc,S,X,DC)
      LARGE-SKUNK\cowan:(R,W,D,WDAC,WO)
      NT AUTHORITY\SYSTEM:(DENY)(S,X)
      BUILTIN\Administrators:(DENY)(S,X)
      LARGE-SKUNK\cowan:(R)
      NT AUTHORITY\SYSTEM:(RX,W)
      BUILTIN\Administrators:(RX,W)
      Everyone:(R)

Successfully processed 1 files; Failed processing 0 files

cowan AT large-skunk ~
$ icacls file2
file2 NT AUTHORITY\SYSTEM:(F)
      BUILTIN\Administrators:(F)
      LARGE-SKUNK\cowan:(F)

Successfully processed 1 files; Failed processing 0 files

So apparently the SID used by the UoW subsystem is not one that has
read access.

Andrey Repin scripsit:

> Remove your symlink in the /home directory and use nsswitch.conf to configure
> your home directory location.

I assume you mean fstab.  I removed the symlink, created a directory, and
set the fstab entry for just my home directory to "noacl".  Then I created
file3 from Cygwin, and icacls reports:

cowan AT large-skunk ~
$ icacls file3
file3 NT AUTHORITY\SYSTEM:(F)
      BUILTIN\Administrators:(F)
      LARGE-SKUNK\cowan:(F)

So that works for all files created in the future, but doesn't do anything
for all the files I already have in Cygwin.

> Then set cygdrive to noacl and try again.

I have set both / and /cygdrive to noacl, so now I can read any newly
created file anywhere on the disk, but existing files are as inaccessible
as ever.  I suspect it is the NULL SID: (DENY) entry that is causing the
problem.  Why does Cygwin do that?  My umask is 022, so all files should
be world readable.

I'm now running "icacls . /reset /t /c /l /q" from /cygdrive/c/cygwin,
which takes real time but should dispose of the problem once and for all.

However, either Cygwin should be more selective about the ACEs it creates,
or UoW should use SIDs somewhat more intelligently.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan AT ccil DOT org
"Make a case, man; you're full of naked assertions, just like Nietzsche."
"Oh, i suffer from that, too.  But you know, naked assertions or GTFO."
                        --heard on #scheme, sorta

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