From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Switching groups with newgrp - how to get the new group with |GetTokenInformation()| ?
Date: Mon, 11 Mar 2024 17:56:59 +0100 [thread overview]
Message-ID: <Ze83202vozq9T8Jj@calimero.vinschen.de> (raw)
In-Reply-To: <CAAvCNcCcfO9br8avaNo6tg-FLHef4aH9P8AVyr95bs9ArTTSJQ@mail.gmail.com>
On Mar 11 02:28, Dan Shelton via Cygwin wrote:
> On Wed, 6 Mar 2024 at 14:01, Corinna Vinschen via Cygwin
> <cygwin@cygwin.com> wrote:
> > On Mar 5 23:38, Dan Shelton via Cygwin wrote:
> > > Always editing /etc/nsswitch.conf
> > > forth and back is not a elegant solution, aside from race conditions
> > > with other users on a system
> >
> > So, here we go again.
> >
> > - What exactly are you trying to accomplish by enumerating the accounts?
> > Maybe you won't actually need it for your task at hand.
>
> We're trying to do several things, including but not limited to:
> - Finding which local groups exist. Part of our customer software
> expects that certain groups exist. Unfortunately the group names vary
> between installations, and sometimes names are prefixed with site
> names. Trying to do all permutations with just getent passwd
> $iteration means too many combinations (>= 4000000). So just
> enumerating all local groups with getent group would be the way to go.
Then just change /etc/nsswitch.conf to enumerate "local" as well
and be done with it.
You can even go so far as to use the Windows enumerator, i.e.,
$ net localgroup
and than script it to use its output as input to getent group
for only the groups you really need info for.
Corinna
next prev parent reply other threads:[~2024-03-11 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 [this message]
2024-04-19 23:44 ` Dan Shelton
2024-04-26 9:04 ` Andrey Repin
2024-02-24 16:57 ` Brian Inglis
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=Ze83202vozq9T8Jj@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).