From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from endymion.arp.harvard.edu (mercury.arp.harvard.edu [140.247.179.71]) by sourceware.org (Postfix) with ESMTPS id A83423858419 for ; Mon, 11 Jul 2022 16:49:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A83423858419 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=huarp.harvard.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=huarp.harvard.edu Received: from [10.15.4.111] (uismhwks351600a.university.harvard.edu [10.1.4.210]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by endymion.arp.harvard.edu (Postfix) with ESMTPSA id 370E726BC0D; Mon, 11 Jul 2022 12:49:06 -0400 (EDT) Message-ID: <2c7cbdb4-1fe4-501b-f5cb-82204b9e4089@huarp.harvard.edu> Date: Mon, 11 Jul 2022 12:49:01 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: chmod g+s ineffective Content-Language: en-US To: moss@cs.umass.edu, Chris Wagner , cygwin@cygwin.com References: <9c053381-4466-ea8a-11d6-ea2e676d3b35@huarp.harvard.edu> <792558531.20220629153952@yandex.ru> <7964c08d-83cb-aab3-5d1c-4a5f0a86bf0a@huarp.harvard.edu> <463526579.20220701025601@yandex.ru> From: Norton Allen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, BODY_8BITS, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2022 16:49:08 -0000 On 7/10/2022 10:33 PM, Eliot Moss wrote: > On 7/10/2022 10:17 PM, Chris Wagner wrote: >>>> On 6/29/2022 9:18 AM, Norton Allen wrote: >>>>>>> On one machine I have, chmod g+s fails to set the sticky bit. >>>>>>> The >>> command >>>>>>> does not return any error, but ls -l continues to show the bit >>>>>>> not set. >>>>>>>      $ mkdir foo >>>>>>>      $ chgrp flight foo >>>>>>>      $ chmod g+ws foo >>>>>>>      $ ls -ld foo >>>>>>>      drwxrwxr-x+ 1 nort flight 0 Jun 29 06:50 foo >> >> Hi.  The permission bits are implemented as normal Window's DACLs >> (Discretionary Access List).  +s is implemented magically with the >> NULL SID.  You can view it from Explorer or with icacls.  Try >> checking the return code (echo $?) from chmod. Also try changing >> perms from Explorer.  You might not be able to set the NULL SID for >> some reason. > > I'd like to add that, for good reason, the Cygwin DACLs do not conform > to the order of entries that some Windows tools prefer.  Don't let any > Windows program/tool reorder the DACLs!  It will break the Cygwin > functionality, and the Cygwin order does not break Windows functionality. > Right. My experience (Windows 10) is that I cannot change perms from Explorer if I don't let them reorder the perms (which I do not). I have been separated from the machine that exhibits the problem, so I have not been able to try the solutions suggested, but expect to have it back in a week or so.