From: Eliot Moss <moss@cs.umass.edu>
To: cygwin <cygwin@cygwin.com>
Subject: A permissions puzzle
Date: Sat, 21 Dec 2019 03:08:00 -0000 [thread overview]
Message-ID: <23ecb190-1382-ed1e-20f2-93b44ddf641f@cs.umass.edu> (raw)
Dear cygwiners --
For a long time I _had_ things working, but somehow in switching over to using
cygwin64 as primary, I messed up permissions on the directories where a backup
program (EaseUS) puts things. I made the permissions similar to elsewhere in
by cygwin hierarchy, but I still cannot chown, chgrp, or chmod files created
by the backup tool - but doing so used to work!
Here is icacls on one of the files:
icacls System_20191220_Inc_v1.pbd
System_20191220_Inc_v1.pbd NULL SID:(I)(DENY)(Rc,S,WD,REA,WEA,X,DC)
BUILTIN\Administrators:(I)(F)
EM-SURFACE-2018\Cygwin:(I)(RX,W,DC)
NT AUTHORITY\SYSTEM:(I)(RX)
Everyone:(I)(RX)
Note that I am an administrator and in in Cygwin (at least "groups" shows
Cygwin).
Here is icacls on the containing directory, which has been "cygwin-ized":
icacls .
. NULL SID:(DENY)(Rc,S,WD,REA,WEA,X,DC)
EM-SURFACE-2018\moss:(F)
EM-SURFACE-2018\Cygwin:(RX,W,DC)
BUILTIN\Administrators:(RX,W,DC)
Everyone:(RX)
NULL SID:(OI)(CI)(IO)(DENY)(Rc,S,WD,REA,WEA,X,DC)
CREATOR OWNER:(OI)(CI)(IO)(F)
EM-SURFACE-2018\Cygwin:(OI)(CI)(IO)(RX,W,DC)
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(RX)
BUILTIN\Administrators:(OI)(CI)(IO)(RX,W,DC)
Everyone:(OI)(CI)(IO)(RX)
And getfacl on the same:
# file: .
# owner: moss
# group: Cygwin
# flags: -s-
user::rwx
group::rwx
group:Administrators:rwx
mask::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:SYSTEM:r-x
default:group:Administrators:rwx
default:mask::rwx
default:other::r-x
So ... why can't I chown, etc., the pbd file, and what needs to change for me
to be able to do so? (I _do_ mostly understand this stuff, but maybe I'm
just too tired and just can;t see the obvious!)
Regards - Eliot
--
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
next reply other threads:[~2019-12-21 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 3:08 Eliot Moss [this message]
2019-12-21 14:35 ` Eliot Moss
2019-12-21 14:50 ` Eliot Moss
2019-12-21 15:42 ` Andrey Repin
[not found] ` <5a63e3e3-6157-e3f4-8bce-e2c671647604@cs.umass.edu>
2019-12-22 13:08 ` Andrey Repin
2019-12-22 17:50 ` Eliot Moss
2019-12-22 22:24 ` Brian Inglis
2019-12-23 6:16 ` Eliot Moss
2019-12-23 14:35 ` Brian Inglis
2019-12-23 16:58 ` Eliot Moss
2019-12-24 23:11 ` 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=23ecb190-1382-ed1e-20f2-93b44ddf641f@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).