From: Norton Allen <allen@huarp.harvard.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: chmod g+ws unsuccessful, "NULL SID" icacls missing
Date: Wed, 8 Feb 2023 16:05:50 -0500 [thread overview]
Message-ID: <0219f7c5-ca4c-bae3-3e13-abfc14c53e01@huarp.harvard.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
I briefly raised this issue months ago and am trying to resolve it again
now.
What I am trying to do is setup permissions so multiple users on one
machine can share full control over a particular directory hierarchy.
On Linux I have usually been able to make things work with:
$ mkdir shared_dir
$ chgrp shared_group shared_dir
$ chmod g+ws shared_dir
$ umask 2
User shells are configured with umask 2 so files they create have group
write. Users belong to shared_group. Files and subdirs created under
shared_dir are all in group shared_group. Files moved in retain their
original group, but the group members still have permission to rename or
delete them.
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.
I suspect there might be a group policy or something that is interfering
with Cygwin's strategy for implementing POSIX permissions. I am pretty
sure this worked correctly at some point in the past.
Has anyone encountered this?
Does group policy seem like a likely suspect? Anyone know which
policy(ies)? I think I might be able to get IT to cut me slack if I knew
what to ask for.
I have also played with using setfacl directly to add permissions, but
as anyone who has read about Cygwin file permissions might guess, that
tends to have mixed/poor results, but I'd be open to any suggestions.
next reply other threads:[~2023-02-08 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 21:05 Norton Allen [this message]
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
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=0219f7c5-ca4c-bae3-3e13-abfc14c53e01@huarp.harvard.edu \
--to=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).