From: xnor <xnoreq@gmail.com>
To: cygwin@cygwin.com
Subject: Re[3]: Issues with ACL settings after updating to the latest cygwin.dll
Date: Mon, 08 Feb 2016 18:33:00 -0000 [thread overview]
Message-ID: <em74965d0e-b8ea-4fcf-b268-ccfdca45d510@gaming> (raw)
In-Reply-To: <ema890e8d3-646a-4b89-9145-20f27329927f@gaming>
>I have the same problem with Transmission.
Sorry for another mail, but I need to make another last correction:
It's not Transmission specific. A simple
$ cd /cygdrive/path/to/download/dir
$ touch test
will result in the same broken permissions for test.
Doing this in $HOME will result in these Windows permissions:
NULL SID
Everyone
<My User>
Nobody (actually non existent S-1-5-21-...)
There are also no warnings and no prompt to re-order permissions.
File permission for an older file (created before cygwin ACL changes):
Everyone
<My User>
Nobody (actually non existent S-1-5-21-...)
So the new ACL implementation simply messes up in directories with
non-cygwin permissions.
--
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 prev parent reply other threads:[~2016-02-08 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 20:46 K Stahl
2016-02-08 14:16 ` Corinna Vinschen
2016-02-08 17:48 ` Re[2]: " xnor
2016-02-08 18:12 ` Re[3]: " xnor
2016-02-08 18:22 ` Corinna Vinschen
2016-02-08 18:20 ` Corinna Vinschen
2016-02-09 20:53 ` Re[2]: " xnor
2016-02-10 2:20 ` Andrey Repin
2016-02-10 17:39 ` Re[2]: " xnor
2016-02-10 18:35 ` Andrey Repin
2016-02-10 11:55 ` Corinna Vinschen
2016-02-10 12:19 ` Corinna Vinschen
2016-02-08 18:33 ` xnor [this message]
2016-02-09 15:02 ` Re[3]: " K Stahl
2016-02-10 11:56 ` 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=em74965d0e-b8ea-4fcf-b268-ccfdca45d510@gaming \
--to=xnoreq@gmail.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).