From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2128 invoked by alias); 10 Feb 2016 18:18:00 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 2007 invoked by uid 89); 10 Feb 2016 18:17:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=cygwin-ug-net, cygwinugnet, joke, scroll X-HELO: mail-wm0-f46.google.com Received: from mail-wm0-f46.google.com (HELO mail-wm0-f46.google.com) (74.125.82.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 10 Feb 2016 18:17:55 +0000 Received: by mail-wm0-f46.google.com with SMTP id c200so41335874wme.0 for ; Wed, 10 Feb 2016 10:17:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:reply-to :user-agent:mime-version:content-type:content-transfer-encoding; bh=qitQlH7cfLRZcP2YVPDaDZz2FDZxGFP2q7e6JOXaSqY=; b=VfrMPdCY7YoYkmMLYknCIN1aDS8X0CgWB/V0vFV/0iTY6BqRhAfLwAR+Itb9x9Fc7V kdbVJjlSACoBY5m0/7Y22fatjop7CXCFOiojauOzkS2YxrXyODKvqpYc15OeEzdacs6C bo9M+5qr+5r/rzM3wURuMC6G6eE71HnWWRbsLNtH/v83oPAZVYs+b3kzbV7etu2HCK/n bQCFc4+DLI9lY1s5hG7nGvVztvWlOhEQQ4cqPeEgiJOALLWj09Py8E2NHMs5Bw+un201 R9hpTx8h5eYsiyXPTNbg/J0QeWsA9oK/m6awguEuCCJKhGMMxqqsWrPbCYXKiMHMRWbb mT7A== X-Gm-Message-State: AG10YOT0AwcNeGnvL+HHe7J5ac9riiKRBiOST5v6RFIQZgcqIEvnMc2f2er5BeJXD7ElhQ== X-Received: by 10.28.220.134 with SMTP id t128mr12284454wmg.61.1455128272934; Wed, 10 Feb 2016 10:17:52 -0800 (PST) Received: from [192.168.1.116] (cm146-196.liwest.at. [81.10.146.196]) by smtp.gmail.com with ESMTPSA id 73sm23597636wmm.7.2016.02.10.10.17.52 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 10 Feb 2016 10:17:52 -0800 (PST) From: xnor To: cygwin@cygwin.com Subject: Re[2]: Issues with ACL settings after updating to the latest cygwin.dll Date: Wed, 10 Feb 2016 18:18:00 -0000 Message-Id: Reply-To: xnor User-Agent: eM_Client/6.0.24316.0 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00142.txt.bz2 >Which warning do you mean here? The "permissions out of order" one. This was not the case before, at=20 least not on my installation, so I don't see how this can be called=20 normal. >Come on, be fair. The new ACL handling started out early 2015, got a >break when I realized that it doesn't work as is, and then got a new >test phase starting back in September. Except for minor bugs it seemed >to work rather well. Nobody reported this effect in all the 4 months=20 >of >test period. You don't actually think I wouldn't have fixed it prior >to the release if I had known about it, do you? 2.4.0-1 was released ~3 weeks ago. I had actually upgraded a few days=20 earlier to a TEST version and noticed that a cygwin downloaded exe=20 couldn't be executed but assumed the exe was corrupt and didn't=20 investigate... Then a few days ago the same thing happened again. Now I'm here. Anyway, clearly most users are just that: users, and not testers that=20 will install and test TEST versions. >They are not supposed to be modifiable in Explorer. If you want to >change permissions on a Cygwin ACL, use chmod or setfacl. Is this a joke? > >> Here is the output from icacls /saveacl for some file: >>=20=20 >>D:P(D;;RPWPDTRC;;;S-1-0-0)(A;;0x1f019f;;;S-1-5-21-559282050-488988736-201= 9639472-1001)(D;;WP;;;AU)(D;;WP;;;SY)(D;;WP;;;BA)(D;;WP;;;BU)(A;;FR;;;S-1-5= -21-559282050-488988736-2019639472-513)(A;;0x1201bf;;;AU)(A;;0x1201bf;;;SY)= (A;;0x1201bf;;;BA)(A;;0x1200a9;;;BU)(A;;FR;;;WD) >Doh, I'm sorry, but I can't read this format very well. Can you please >again send the standard icacls output as well as the output from=20 >getfacl >of the parent dir and the created file? I'd like to have this problem >fixed, but I need your help. As I said, it works fine for me and=20 >without >being able to reproduce I'm somewhat at a loss. You can import this by putting it in a textfile and using icacls=20 testfile /restore acl.txt. As I've said before, my Windows is German. icacls output will be=20 localized. Do you really want that? What I posted is the only portable way to share ACLs. > >> Here is what's "normal" for Windows if I create a file under a new=20 >>folder on >> C: in Explorer: > >If you don't want POSIX perms, but standard Windows perms, use the=20 >"noacl" >mount option. See=20 >https://cygwin.com/cygwin-ug-net/using.html#mount-table I guess that is my only option right now. > >> Here is what I would expect: >> MyUser is in the group Administrators. Given the inherited=20 >>permissions above >> a Windows-created file should be shown as "-rwxrwxr--+ MyUser >> Administrators"? > >Sorry, can't do that, *unless* you make "Administrators" the primary >group in your user token(*). Ok, so the group is "None". No big deal. So what about fixing the permissions like I described? So the permissions would be "-rwx------+ MyUser None" in Cygwin for a=20 Windows-created file with default ACL. By using the inherited default ACLs there should be at most 3 additional=20 ACLs (+1 for NULL SID whatever that is doing): - deny r/w/x for user ("MyUser") - allow r/w/x for group ("None") - allow r/w/x for other ("Everyone") And leaving the inherited ones untouched, right? But if you scroll up you will see that in my system Cygwin kills the=20 inheritance and I end up with 12 new ACL entries for each file. -- 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