This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygwin potentially corrupting permissions?

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

$ ./ .
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

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

$ ./ /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.


> 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:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]