public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Norton Allen <allen@huarp.harvard.edu>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: chmod g+ws unsuccessful, "NULL SID" icacls missing
Date: Fri, 10 Feb 2023 19:41:26 +0100	[thread overview]
Message-ID: <Y+aP1jATyXJ6hs7n@calimero.vinschen.de> (raw)
In-Reply-To: <1edf29a6-9fec-2964-cf99-e722e3121f4f@huarp.harvard.edu>

On Feb 10 11:42, Norton Allen via Cygwin wrote:
> On 2/9/2023 4:09 PM, Corinna Vinschen wrote:
> > On Feb  9 13:25, Norton Allen via Cygwin wrote:
> > > On 2/8/2023 4:05 PM, Norton Allen via Cygwin wrote:
> > > > [...]
> > > > The problem:
> > > > 
> > > > $ chmod g+ws fails to set the 's' bit, and the resulting icacls output
> > > > does not contain any "NULL SID" entries. I am seeing the same problem on
> > > > (at least) two different systems setup by my organization. One of these
> > > > was just re-imaged and I installed Cygwin yesterday with no customized
> > > > configurations. AV is Windows Defender, but I suspect if that were the
> > > > culprit, there would have been more noise.
> > > > [...]
> > > [...]
> > > Any idea what g+s should be doing? Any more/better information I can
> > > provide?
> > What you observe is a bug in Cygwin, plain and simple.  Without going
> > into too much detail, part of the problem could never be observed with
> > older coreutils, which we had to live with for much too long in the
> > Cygwin distro.  The newer coreutils handles permissions slightly
> > differently and that dropped the mask from the buggy code.
> > 
> > I applied a patch which, hopefully, fixes this problem (in fact, plural,
> > "these problems").
> > 
> > A new Cygwin test release 3.5.0-0.162.g498fce80ef33 is just being built
> > and should be up in an hour or so.  You can simply install it via
> > Cygwin's setup tool as soon as it's on your favorite mirror.
> > 
> > If it works as desired, it will be part of the next Cygwin bugfix
> > release 3.4.6.
> 
> Corinna,
> 
> The fix seems to work like a charm! And I am happy to be wrong about the
> source of the problem.

Great, thanks for testing!


Corinna

      reply	other threads:[~2023-02-10 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 21:05 Norton Allen
2023-02-09 18:25 ` Norton Allen
2023-02-09 21:09   ` Corinna Vinschen
2023-02-10 16:42     ` Norton Allen
2023-02-10 18:41       ` Corinna Vinschen [this message]

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=Y+aP1jATyXJ6hs7n@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=allen@huarp.harvard.edu \
    --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).