public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-0.7
Date: Wed, 22 Apr 2015 18:35:00 -0000	[thread overview]
Message-ID: <877ft480zp.fsf@Rainer.invalid> (raw)
In-Reply-To: <20150422090440.GB3657@calimero.vinschen.de> (Corinna Vinschen's	message of "Wed, 22 Apr 2015 11:04:40 +0200")

Corinna Vinschen writes:
> Hmm.  Can you try the same with the latest developer snapshot I just
> created?  I found this problem which created undesired DENY ACEs,
> maybe this was the reason /knock on wood/.

I ran out of time, but I've managed to install the snapshot and did a
quick test before going home.  The ACL looks saner than before and I can
regain access via chmod, so that's good.  The basic problem however
remains and I'm really not sure if that's a bug in rsync or in Cygwin or
even a bug at all.

The file to be copied has, as stated before, access granted only via a
share group (actually three of them, but that's not a factor).  So
CREATOR OWNER, CREATOR group, the original owner of the file and myself
(owner of the newly created file) have no DACL entry on the original
file and the resulting file mode is "---rwx---+".  For "rsync -av" this
means that after the copy the mode is set to 0060 and that explicitly
locks out (via DENY) CREATOR OWNER CREATOR GROUP and myself.  That gives
the same POSIX modes, but not the same access rights of course.  For
"rsync -av --acls" the same happens and then some ACL are copied over
from the original file, which still doesn't get me access since the
DENY ACL is first in the list.

This might be a hole in the ACL mapping to POSIX file modes.  The way I
see it the reported file mode should actually be "rwxrwx---+" for the
original file since that's the effective access granted by Windows and
there are no POSIX flags on the original file (via NULL SID).  Just like
on POSIX (where it's done via mask) the user flags can only be cleared
in this situation by an explicit chmod (which then gets implemented via
DENY ACL I suppose).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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

  reply	other threads:[~2015-04-22 18:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 11:03 Corinna Vinschen
2015-04-17 20:10 ` Achim Gratz
2015-04-18  8:39   ` Corinna Vinschen
2015-04-18  9:47     ` Achim Gratz
2015-04-18 10:20       ` Corinna Vinschen
2015-04-18 10:48         ` Achim Gratz
2015-04-18 11:07           ` Corinna Vinschen
2015-04-19  6:05             ` Achim Gratz
2015-04-21  9:33 ` Achim Gratz
2015-04-21 12:16   ` Corinna Vinschen
2015-04-21 17:19     ` Achim Gratz
2015-04-22  9:04       ` Corinna Vinschen
2015-04-22 18:35         ` Achim Gratz [this message]
2015-04-23  8:34           ` Corinna Vinschen
2015-04-23 18:45             ` Achim Gratz
2015-04-23 19:49               ` Corinna Vinschen
2015-04-24  2:14                 ` random user

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=877ft480zp.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).