From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [TESTERS needed] New POSIX permission handling
Date: Fri, 17 Apr 2015 10:06:00 -0000 [thread overview]
Message-ID: <20150417100646.GR3657@calimero.vinschen.de> (raw)
In-Reply-To: <20150417073043.GK3657@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]
On Apr 17 09:30, Corinna Vinschen wrote:
> Hi Ismail,
>
> On Apr 16 09:48, Ismail Donmez wrote:
> > Corinna Vinschen-2 wrote
> > > On Apr 16 09:09, Ismail Donmez wrote:
> > >> [~/src/mutt]> chmod +x config.status
> > >> chmod: changing permissions of ‘config.status’: Permission denied
>
> This is really surprising.
>
> > [~/src/mutt]> icacls config.status
> > config.status NULL SID:(DENY)(Rc,S,REA,X,DC)
> > UX31A\ismail:(F)
> > UX31A\ismail:(RX)
> > NT AUTHORITY\SYSTEM:(RX,W,DC)
> > BUILTIN\Administrators:(RX,W,DC)
> > Everyone:(RX)
> >
> > Successfully processed 1 files; Failed processing 0 files
> >
> > [~/src/mutt]> icacls .
> > . NULL SID:(DENY)(Rc,S,REA,X,DC)
> > UX31A\ismail:(F)
> > UX31A\ismail:(RX)
> > NT AUTHORITY\SYSTEM:(RX,W,DC)
> > BUILTIN\Administrators:(RX,W,DC)
> > Everyone:(RX)
> > NULL SID:(OI)(CI)(IO)(DENY)(Rc,S,REA,X,DC)
> > CREATOR OWNER:(OI)(CI)(IO)(F)
> > CREATOR GROUP:(OI)(CI)(IO)(RX)
> > NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(RX,W,DC)
> > BUILTIN\Administrators:(OI)(CI)(IO)(RX,W,DC)
> > Everyone:(OI)(CI)(IO)(RX)
>
> I created the exact same scenario with the exact same ACLs, just with my
> own account as user and group, and I can't reproduce a "Permission
> denied". chmod simply works for me. Weird.
>
> While looking into this I found some other problems in this owner==group
> scenario, so I applied a few patches. I'm just creating new developer
> snapshots and a 2.0.0-0.6 test release.
>
> It would be nice if you could update, test again, and if the problem
> still occurs, I think I'll need an strace of the above chmod call as
> in:
>
> $ strace -o chmod.trace chmod +x config.status
>
> This combined with the icacls of the ACLs of config.status and the
> parent dir, just to be sure the new Cygwin created the same ACLs.
I think I found the culprit. I'll uploade a -0.7 test release in
the next hour or so.
Thanks for testing,
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-17 10:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 10:07 Corinna Vinschen
2015-04-10 21:13 ` Warren Young
2015-04-11 9:35 ` Corinna Vinschen
2015-04-11 0:00 ` Steven Penny
2015-04-11 9:40 ` Corinna Vinschen
2015-04-11 10:07 ` Corinna Vinschen
2015-04-11 16:26 ` Ernie Rael
2015-04-12 8:22 ` Corinna Vinschen
2015-04-11 10:23 ` Corinna Vinschen
2015-04-11 10:47 ` Steven Penny
2015-04-11 14:30 ` Corinna Vinschen
2015-04-11 16:05 ` Andrey Repin
2015-04-12 17:37 ` Adam Dinwoodie
2015-05-16 2:39 ` Steven Penny
2015-05-17 7:44 ` Duncan Roe
2015-05-19 7:52 ` Jiří Engelthaler
2015-04-11 8:47 ` Achim Gratz
2015-04-11 9:02 ` David Macek
2015-04-11 9:08 ` Achim Gratz
2015-04-11 9:51 ` David Macek
2015-04-11 11:51 ` Achim Gratz
2015-04-11 10:00 ` Corinna Vinschen
2015-04-11 12:36 ` David Macek
2015-04-11 14:31 ` Corinna Vinschen
2015-04-11 9:44 ` Corinna Vinschen
2015-04-11 11:11 ` Bryan Berns
2015-04-11 14:32 ` Corinna Vinschen
2015-04-11 16:05 ` Andrey Repin
2015-04-11 17:11 ` donmez
2015-04-12 8:35 ` Corinna Vinschen
2015-04-12 13:21 ` İsmail Dönmez
2015-04-12 14:25 ` Corinna Vinschen
2015-04-15 15:42 ` Corinna Vinschen
2015-04-16 10:20 ` Ismail Donmez
2015-04-16 11:03 ` Corinna Vinschen
2015-04-16 16:09 ` Ismail Donmez
2015-04-16 16:24 ` Corinna Vinschen
2015-04-16 16:48 ` Ismail Donmez
2015-04-17 7:30 ` Corinna Vinschen
2015-04-17 10:06 ` Corinna Vinschen [this message]
2015-04-17 15:17 ` Ismail Donmez
2015-04-17 16:22 ` Corinna Vinschen
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=20150417100646.GR3657@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).