From: L A Walsh <cygwin@tlinx.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: objects created in a dir w/cygwin mangled perms; inherit no-access
Date: Sat, 03 Jul 2021 22:44:10 -0700 [thread overview]
Message-ID: <60E14AAA.4000404@tlinx.org> (raw)
Trying to track down exact conditions for a simpler testcase
for a weird error message in tar and ran across this...
in directory 'SI':
/progd/Microsoft/../Tools/Sysinternals> ll -ad SI
drwxrwxr-x+ 1 0 Jul 3 16:28 SI/
w/umask:
> umask
0002
I make dir 'newdir':
> mkdir newdir
and ls -lgG shows:
d---rwxr-x+ 1 0 Jul 3 16:40 newdir/
No access for user(me).
I ran into this because trying to enter the directory in
explorer I got no access! Trying to look at the perms, I
get warnings about the rights possibly being out of order until
eventually, if I want to proceed, it claims it has to reorder them.
This seems to have come from some weird setting that
seems to come from Cygwin, with 5 deny records at the front
for NULL, 3 local accounts and 1 domain account (me)...
and the local accts ... also me of a sort.
Then come various allows, some of them that would seem
to undo some of the denies, but its really dependent on
order -- which explorer says is suspect...
Fine...so the results when I did the "mkdir newdir", were
such that ended up with u-wrx, and no access in explore?
Of course I can overide, but why are such weird acls on
this anyway? -- especially when it doesn't seem to really
work?
next reply other threads:[~2021-07-04 5:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 5:44 L A Walsh [this message]
2021-07-04 14:20 ` Andrey Repin
2021-07-06 13:55 ` L A Walsh
2021-07-07 18:43 ` Andrey Repin
2021-07-15 7:02 ` L A Walsh
2021-07-15 8:23 ` Sam Edge
2021-08-23 19:31 ` L A Walsh
2021-08-24 6:19 ` Sam Edge
2021-07-16 4:44 ` Andrey Repin
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=60E14AAA.4000404@tlinx.org \
--to=cygwin@tlinx.org \
--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).