From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-3
Date: Tue, 14 Apr 2015 15:12:00 -0000 [thread overview]
Message-ID: <20150414151255.GM7343@calimero.vinschen.de> (raw)
In-Reply-To: <b962c3b9b72680589885fce04084640e.squirrel@webmail.xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
On Apr 14 17:01, Houder wrote:
> %% uname -a
> CYGWIN_NT-6.1-WOW Seven 2.0.0(0.287/5/3) 2015-04-14 10:45 i686 Cygwin
> %% pwd
> /home/Test
> %% touch alfa
> %% chmod 460 alfa
> %% echo aha > alfa
> bash: alfa: Permission denied # no problem here ...
>
> %% getfacl alfa
> # file: alfa
> # owner: Test
> # group: None
> user::r--
> group::r-x
> mask:rw-
> other:---
> %% icacls alfa
> alfa NULL SID:(DENY)(Rc,S,WEA,X,DC)
> Seven\Test:(DENY)(S,WD,AD,WEA,DC)
> Seven\Test:(R,D,WDAC,WO,WA)
> Seven\None:(DENY)(S,X)
> Seven\None:(RX)
> Everyone:(Rc,S,RA)
> Successfully processed 1 files; Failed processing 0 files
> %%
This looks exactly like the ACL created by -0.3. It produces this MASK
value. The rest is just the logical consequence. But it doesn't do
that for me:
$ uname -a
CYGWIN_NT-6.3 vmbert8164 2.0.0(0.287/5/3) 2015-04-14 10:47 x86_64 Cygwin
$ touch alfa
$ getfacl alfa
# file: alfa
# owner: corinna
# group: vinschen
user::rw-
group::r--
other:r--
$ chmod 460 alfa
$ getfacl alfa
# file: alfa
# owner: corinna
# group: vinschen
user::r--
group::rw-
other:---
$ icacls alfa | cat
alfa NULL SID:(DENY)(Rc,S)
VINSCHEN\corinna:(DENY)(S,WD,AD,WEA,DC)
VINSCHEN\corinna:(R,D,WDAC,WO,WA)
VINSCHEN\vinschen:(R,W)
Everyone:(Rc,S,RA)
The only reason I can think of is that the parent dir has default
permissions which imply the mask value already. So, what does
`icacls . | cat' in this directory print?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-14 15:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 16:10 Houder
2015-04-14 8:58 ` Corinna Vinschen
2015-04-14 14:18 ` Houder
2015-04-14 14:50 ` Corinna Vinschen
2015-04-14 15:01 ` Houder
2015-04-14 15:12 ` Corinna Vinschen [this message]
2015-04-14 15:26 ` Houder
2015-04-14 15:45 ` Corinna Vinschen
2015-04-14 16:32 ` Houder
2015-04-14 18:21 ` Corinna Vinschen
2015-04-14 18:38 ` Houder
2015-04-15 7:13 ` Corinna Vinschen
2015-04-15 7:46 ` Houder
2015-04-15 9:04 ` Corinna Vinschen
2015-04-14 14:27 ` Achim Gratz
2015-04-14 14:52 ` Corinna Vinschen
2015-04-14 15:35 ` Achim Gratz
2015-04-14 15:53 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2015-04-12 19:23 Corinna Vinschen
2015-04-12 21:19 ` Bryan Berns
2015-04-13 7:17 ` Corinna Vinschen
2015-04-13 7:32 ` Corinna Vinschen
2015-04-13 11:13 ` Bryan Berns
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=20150414151255.GM7343@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).