public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: cygwin@cygwin.com
Subject: Re: Files and folders created with invalid ACL
Date: Sun, 21 Jun 2020 20:42:55 +0200	[thread overview]
Message-ID: <rco9ng$1krj$1@ciao.gmane.io> (raw)
In-Reply-To: <2671dec4-b4e5-e687-7d82-4c465b1231b6@cs.umass.edu>

* Eliot Moss (Sun, 21 Jun 2020 14:10:21 -0400)
> 
> On 6/21/2020 1:56 PM, Thorsten Kampe wrote:
> > Hello,
> > 
> > I'm experiencing the issue described here[1]: files and folders
> > created with Cygwin utilities like touch and mkdir have an
> > incorrect ACL ("The access control list (ACL) structure is
> > invalid (os error 1336)").
> > 
> > icacls test.txt /verify
> > test.txt: Ace entries not in canonical order.
> > 
> > Interestingly the issue does not occur with files created in
> > the user's Cygwin home directory but - for instance - in the
> > Documents folder of the user's Windows profile.
> > 
> > This is a fresh Cygwin installation on a test system. Has
> > anyone found a solution?
> > 
> > [1] http://cygwin.1069669.n5.nabble.com/Issues-with-ACL-
> > settings-after-updating-to-the-latest-cygwin-dll-td124123.html
> 
> This is normal, and has to do with how Cygwin arranges to model,
> within the Windows ACL permissions system, some features of the
> Posix permissions system. Don't "fix" the ACLs - that can make
> the Posix functionality break.  While the entries are not in
> canonical order, they work fine :-) ...

"The access control list (ACL) structure is invalid (os error 
1336". That's an error and not a cosmetic issue. Other tools 
from the Unix world do not work fine with files that have an 
invalid ACL: <https://github.com/Peltoche/lsd/issues/334
#issuecomment-647119819>

Thorsten


  reply	other threads:[~2020-06-21 18:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 17:56 Thorsten Kampe
2020-06-21 18:10 ` Eliot Moss
2020-06-21 18:42   ` Thorsten Kampe [this message]
2020-06-21 19:12     ` Thorsten Kampe
2020-06-22 17:20 ` Andrey Repin
2020-06-22 18:08   ` Thorsten Kampe
2020-06-22 19:59     ` Eliot Moss
2020-06-22 21:13       ` Brian Inglis
2020-06-22 21:57       ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='rco9ng$1krj$1@ciao.gmane.io' \
    --to=thorsten@thorstenkampe.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).