public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Chris Wagner <wagnerc@plebeian.com>, cygwin@cygwin.com
Subject: Re: chmod g+s ineffective
Date: Sun, 10 Jul 2022 22:33:47 -0400	[thread overview]
Message-ID: <d661eca3-484b-258d-7ba6-7af22347d27a@cs.umass.edu> (raw)
In-Reply-To: <ddda74cf906b99988ecbbb30f6f5ef0a@plebeian.com>

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.

Best - Eliot Moss

  reply	other threads:[~2022-07-11  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 12:12 Norton Allen
2022-06-29 12:39 ` Andrey Repin
2022-06-29 14:18   ` Norton Allen
2022-06-29 17:51     ` Norton Allen
2022-06-30 23:56       ` Andrey Repin
2022-07-11  2:17         ` Chris Wagner
2022-07-11  2:33           ` Eliot Moss [this message]
2022-07-11 16:49             ` Norton Allen

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=d661eca3-484b-258d-7ba6-7af22347d27a@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    --cc=wagnerc@plebeian.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).