From: Andrey Repin <anrdaemon@yandex.ru>
To: Thorsten Kampe <thorsten@thorstenkampe.de>, cygwin@cygwin.com
Subject: Re: Files and folders created with invalid ACL
Date: Mon, 22 Jun 2020 20:20:35 +0300 [thread overview]
Message-ID: <1335658627.20200622202035@yandex.ru> (raw)
In-Reply-To: <rco6vs$30d$1@ciao.gmane.io>
Greetings, Thorsten Kampe!
> 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.
This is normal. All conformant drivers MUST be able to correctly process such
ACL's. "Non-canonical" does not mean "invalid".
> 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
Needs more specifics.
How did you set your fstab, particularly cygdrive prefix? Any extra mounts?
How did you modify nsswitch?
--
With best regards,
Andrey Repin
Monday, June 22, 2020 20:10:13
Sorry for my terrible english...
next prev parent reply other threads:[~2020-06-22 17:35 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
2020-06-21 19:12 ` Thorsten Kampe
2020-06-22 17:20 ` Andrey Repin [this message]
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=1335658627.20200622202035@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=thorsten@thorstenkampe.de \
/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).