public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: Permissions issues after installing Windows 10
Date: Fri, 3 Jun 2022 10:42:23 -0600	[thread overview]
Message-ID: <CANV9t=Tox=Ls+q=TCk7Zxk6ZRurgy-LRuUm7EGA67vCSAnFidA@mail.gmail.com> (raw)
In-Reply-To: <75c20491-164b-b3cb-55d0-a482240842c3@pdc.ca>

On Fri, Jun 3, 2022 at 6:23 AM Brent Epp wrote:

I would think so too, but that doesn't appear to be happening. If it
> makes a difference, the SID actually starts with S-1-5-21. I have to
> manually take ownership in order to even access the files at all.
>

Explained another way: According to
https://docs.microsoft.com/en-us/windows/win32/secauthz/well-known-sids -

Constant: SECURITY_NT_NON_UNIQUE
String Value: S-1-5-21
Identifies: SIDS are not unique.

SIDs starting with S-1-5-21 are non-unique, which means basically the SID
is made unique by the addition of a RID (relative identifier).

If the SID starts with S-1-5-21 and ends in 500, it is the local
"Administrator" account of some computer (or domain).

In other words, S-1-5-21 SIDs are computer or domain accounts that the
system couldn't resolve when it enumerated the ACL.

You can see SIDs for local accounts on a machine from PowerShell (all one
line):

Get-WmiObject -Query "SELECT * FROM Win32_UserAccount WHERE
LocalAccount='TRUE'" | Select-Object Name,SID

Note that in the output, these SIDs will start with S-1-5-21 and end with
various RIDs.

Bill

      parent reply	other threads:[~2022-06-03 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 15:00 Brent Epp
2022-05-08 15:35 ` Andrey Repin
2022-06-02 12:43   ` Brent Epp
2022-06-02 15:14     ` Bill Stewart
2022-06-03 12:23       ` Brent Epp
2022-06-03 12:47         ` Achim Gratz
2022-06-03 16:42         ` Bill Stewart [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='CANV9t=Tox=Ls+q=TCk7Zxk6ZRurgy-LRuUm7EGA67vCSAnFidA@mail.gmail.com' \
    --to=bstewart@iname.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).