public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: John Ruckstuhl <john.ruckstuhl@gmail.com>
To: cygwin@cygwin.com, John.Ruckstuhl@gmail.com
Subject: Re: cygwin utils can access directory and its contents, but W10 utils claim to have no access, why?
Date: Mon, 22 Jan 2024 10:59:26 -0800	[thread overview]
Message-ID: <CAOBROv25QD8w703nim4yU0EzXz-Gw3WzrsUicYbm6q9u5y0ozQ@mail.gmail.com> (raw)
In-Reply-To: <Za454au_liWSTwhw@calimero.vinschen.de>

Thanks for the replies Brian & Corinna, I learned a lot.

On Mon, Jan 22, 2024 at 1:48 AM Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> Users in the Administrators group have these privileges in their user
> token.  Under UAC, both privileges are removed from the token.  In an
> elevated shell, though, both privileges are present.
>
> The funny thing here is this: While both privileges are present in the
> token, they are disabled by default.
>
> They have to be enabled explicitely before you can exercise the
> privileges.  Usually you do this in the same application
> programatically.

Now I see...
Local administrator Bob reports his User Access Token info
(with Windows whoami, not cygwin whoami)
    C:\>whoami /priv

    PRIVILEGES INFORMATION
    ----------------------

    Privilege Name                            ... State
    ========================================= ... ========
      ...
      SeBackupPrivilege                         ... Disabled
      SeRestorePrivilege                        ... Disabled
      ...

      C:\>

Thanks very much.
John Ruckstuhl

  reply	other threads:[~2024-01-22 18:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  6:18 John Ruckstuhl
2024-01-22  7:33 ` Brian Inglis
2024-01-22  9:48 ` Corinna Vinschen
2024-01-22 18:59   ` John Ruckstuhl [this message]
2024-04-03  2:07     ` John Ruckstuhl

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=CAOBROv25QD8w703nim4yU0EzXz-Gw3WzrsUicYbm6q9u5y0ozQ@mail.gmail.com \
    --to=john.ruckstuhl@gmail.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).