DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type; q=dns; s=default; b=xKe4
	zapM+vhEGwLpN/jFcvrD0ho0b2TQoRheR/E+G6HuxNqTTyBXzKu+SDgPDMAmkcpf
	gzv21mm0Q1Ca86Kl+VkrgbMCXGiGfDeu++6kuWjg3AUc4j3PhYSJpVd1SA73uB2C
	h8LOyJczNUk9icVNuMAPvtb26coDzNGUA4YCTG8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <56044EBD.8090904@tlinx.org>
References: <CAGpXXZKUQtAbrQ80VDHZhy0aZtzG+5fDB7bcYz-kwQ3Kgx6ueQ@mail.gmail.com> <560366EE.5020207@tlinx.org> <CAGpXXZJeWs33BJi7qROduZEhTx1pXXXseTbfXu+QP8+cf_r5hQ@mail.gmail.com> <56043BA4.7040405@tlinx.org> <CAGpXXZLrourgJ39=n4M8kEKeF7tT3fCTafvLaSfZuHh62ffmUA@mail.gmail.com> <56044EBD.8090904@tlinx.org>
From: Greg Freemyer <greg.freemyer@gmail.com>
Date: Thu, 24 Sep 2015 22:17:37 -0400
Message-ID: <CAGpXXZLO_1MQFj3mNO6RubqHLLnh=9G2RDV=PQB0rM2aQP2GqA@mail.gmail.com>
Subject: Re: cygwin potentially corrupting permissions?
To: Linda Walsh <cygwin@tlinx.org>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Content-Type: text/plain; charset=UTF-8

On Thu, Sep 24, 2015 at 3:27 PM, Linda Walsh <cygwin@tlinx.org> wrote:
> Greg Freemyer wrote:
>>
>>
>> Totally logical, but not accurate. )
>
> ---
>         What does it say if you do an 'lsacl' on "." (the parent directory).

$ ./lsacl.sh .
[u::---,g::---,g:root:rwx,g:Authenticated
Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:---/u::---,g::---,g:root:rwx,g:Authenticated
Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:---] .

But maybe this is interesting.  I just created 2 folders in C:\   .  I
did it at the C:\ level because I can't imagine I ever modified the
ACLs on C:\.

Anyway, one directory was created via "mkdir" in cygwin.  The other
via the file explorer.  Look at how different the ACLs are:

$ mkdir /cygdrive/c/Test-dir-created-in-cygwin

$ ./lsacl.sh /cygdrive/c/Test-dir-created-in-cygwin/
[u::rwx,g::r-x,g:root:rwx,g:Authenticated
Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:r-x/u::rwx,g::r-x,g:root:rwx,g:Authenticated
Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:r-x]
/cygdrive/c/Test-dir-created-in-cygwin/

$ ./lsacl.sh /cygdrive/c/Test-dir-created-in-file-explorer/
[u::---,g::---,g:root:rwx,g:Authenticated
Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:---/u::---,g::---,g:root:rwx,g:Authenticated
Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:---]
/cygdrive/c/Test-dir-created-in-file-explorer/

What's that about?  Again I'm not expert at ACLs, but the ACLs on the
directory created via File Explorer look really strange to me.

>         This is a local file system?  NTFS?

Yes, C: drive. It's my local system drive on both computers and NTFS
on both machines.

> Do you have process hacker?  Maybe the writing process has a different
> integrity label or such.

No, but let me know if you still want me to pursue that.  For now I'm
thinking the ACLs on folders created via File Explorer are somehow
getting screwed up.

Thanks
Greg

> Process hacker lets you see what the integrity labels are on files,
> but to see what they are on files you'd have to d/l another util.
> (chml/regil
>
>>
>> - cygwin is not properly maintaining the permissions when it manipulates a
>> file
>
> ----
>         May not be able to ... Windows trumps cygwin.
> MS-regularly screws w/windows, .. it's like switching to a new
> init system every month... ok.. maybe not quite that bad...
>
>>
>> Either way, I would really like a solution that doesn't involve a
>> manual chmod for every file I create via the normal Windows interface
>> and which I want to work with it in cygwin.
>
> ===
>         I can understand that -- that's sorta why I haven't upgraded
> my cygwin lately -- She spent alot of time solving a problem that didn't
> really appear on my system, so changing the whole security system -- well
> I already know that cygwin doesn't respect existing standards or sources.
> (overwrite windows mount points created -- and is shipping a login that
> zeros your environment -- even when passed switch to not do so --
> effectively
> wipes your windows session -- forcing users to copy sessions from static
> files to get around the problem.
>

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