DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 63SDPZ9N121224
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D15474B9DB5D
MIME-Version: 1.0
References: <CALWcw=HNsScw6AcFU5-g1nvy7g+NRWZ-B2LMFFaHAoTWkkN17g@mail.gmail.com>
 <CANV9t=TqRJ1NMYKTaq5Y2b4Dfw+tf+inPQ3AUddmA-+2pONHag@mail.gmail.com>
 <CALWcw=FDxArr8cRMG6T8P0ADZs6t=3sMpoZkXygNCsa2Hfn3bQ@mail.gmail.com>
In-Reply-To: <CALWcw=FDxArr8cRMG6T8P0ADZs6t=3sMpoZkXygNCsa2Hfn3bQ@mail.gmail.com>
Date: Tue, 28 Apr 2026 07:24:14 -0600
Message-ID: <CANV9t=QX6jKVM4AOjLxAQO7ztPQdsNgDCWEwwxS0jHbBwgbQ-g@mail.gmail.com>
Subject: Re: Getting Windows "MACHINE SID" without fork() & exec()?
To: cygwin@cygwin.com
From: William Stewart via Cygwin <cygwin@cygwin.com>
Reply-To: bstewart@iname.com
Cc: William Stewart <abqbill@gmail.com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On Thu, Apr 23, 2026 at 11:24 AM Takeshi Nishimura wrote:

Pass MACHINE SID around in a shell script. Doing that by calling
> powershell each time is very expensive, around 92% of the scripts
> whole runtime


Can you describe what you mean by "calling powershell each time"? Getting
the computer's SID in PowerShell can be quite efficient if you use P/Invoke.

But aside from that, what problem are you solving that requires getting the
machine's SID?

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple