public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Switching groups with newgrp - how to get the new group with |GetTokenInformation()| ?
Date: Sat, 24 Feb 2024 09:57:11 -0700	[thread overview]
Message-ID: <03d0eb6d-2f0a-465a-8fb6-fa9bbbd19c12@SystematicSW.ab.ca> (raw)
In-Reply-To: <CAAvCNcCHAVooYX2_tUHHnUYvWRKHWhBwxmKws7AcqjOo-sQd+g@mail.gmail.com>

On 2024-02-23 14:15, Dan Shelton via Cygwin wrote:
> On Fri, 23 Feb 2024 at 19:45, Roland Mainz via Cygwin wrote:
>> After that /usr/bin/chgrp on Cygwin works on the NFSv4.1 filesystem,
>> but if I do a /usr/bin/newgrp+/usr/bin/touch it will not create files
>> with that new group, because nfsd_debug.exe only sees the default
>> primary group, not the new primary group set by /usr/bin/newgrp.
>>
>> Or is there a mistake - do I have to add the current user to the
>> Windows localgroup first somehow (like usermod on Linux) ?
> 
> Yes, there is a mistake. You have to add the intended user to that group.
> 
> Example:
> net localgroup mywingrp1 mywinuser44 /add
> 
> HOWEVER, there is another Cygwin bug:
> "getent group mywingrp1" does not list any group members, even after
> "net localgroup mywingrp1 mywinuser44 /add", which is a POSIX
> violation.

No POSIX violation as getent and nsswitch came from Solaris, and despite 
adoption by Linux, BSDs, and Cygwin, is not standardized as of SUSv5? draft 
202x_d4.1.

Cygwin `getent group` depends on `/etc/nsswitch.conf` settings, defaults to 
`files db`, and lists the contents of the entries in `/etc/group` and/or 
Security Account Manager SAM groups and/or Active Directory AD groups (could 
take a long while initially and is faster with cygserver caching).

See `getent(1)`.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  parent reply	other threads:[~2024-02-24 16:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 17:38 Roland Mainz
2024-02-22 19:11 ` Corinna Vinschen
2024-02-23 13:03   ` Roland Mainz
2024-02-23 15:47     ` Corinna Vinschen
2024-02-23 18:45       ` Roland Mainz
2024-02-23 21:15         ` Dan Shelton
2024-02-24 13:11           ` Corinna Vinschen
2024-03-05 22:38             ` Dan Shelton
2024-03-06 13:01               ` Corinna Vinschen
2024-03-09 21:26                 ` Glenn Strauss
2024-03-11  1:30                   ` Dan Shelton
2024-03-11  3:49                     ` Brian Inglis
2024-03-11 16:54                   ` Corinna Vinschen
2024-03-11  1:28                 ` Dan Shelton
2024-03-11 16:56                   ` Corinna Vinschen
2024-04-19 23:44                     ` Dan Shelton
2024-04-26  9:04                       ` Andrey Repin
2024-02-24 16:57           ` Brian Inglis [this message]
2024-02-24 12:53         ` Corinna Vinschen
2024-02-24 14:38   ` Will all SIDs fit into |SECURITY_MAX_SID_SIZE| bytes ? / was: " Roland Mainz
2024-02-24 18:57     ` Corinna Vinschen
2024-02-25 21:04       ` Roland Mainz
2024-02-25 22:32         ` gs-cygwin.com
2024-02-26  4:17           ` gs-cygwin.com
2024-02-26 16:12           ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2024-02-26  9:20         ` 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=03d0eb6d-2f0a-465a-8fb6-fa9bbbd19c12@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).