public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lord Laraby <lord.laraby@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Question about UAC and bash/cygwin
Date: Thu, 16 Aug 2012 08:51:00 -0000	[thread overview]
Message-ID: <CAG9p0OS3HKvaE9ye6g3vKP4kXPZGBw=uc-ELb0WcvdPefGQmFg@mail.gmail.com> (raw)
In-Reply-To: <502C6B1C.5030900@cygwin.com>

Larry Hall (Cygwin) wrote:
> On 8/15/2012 5:39 AM, Lord Laraby wrote:
>
>> Sorry if the questions are a bit too numerous. I wish I could just
>> siphon knowledge from Corinna's brain.:)
>
> Then that would leave her with none!

I wouldn't need *all* of her knowledge of course. Just a small amount
would improve my understanding immensely.

>
> Probably the key point that you're stumbling over is the fact that
> when you're elevating your user's privileges, you're not changing
> from that user to 'root' but rather just enabling privileges the user
> is allowed to use.  'whoami' will not change.  This is a difference
> between Windows and Unix/Linux security models.

I see that, of course. But it was always my assumption (a warranted
one I expect from some of the other posts I've read) that since
neither su, nor sudo, nor newgrp, login allows becoming root in cygwin
- and any administrator on a linux box can use those to become root.
So then, privilege elevation would be the closest analogy (for WIndows
7 etc.). After all, there is no *real* user named root on 99.9% of
boxes out there. An administrator gets the power to become root for a
time. Same with UAC, etc.

So0, you see where I'm coming from with my thinking, an Administrator
is adble to become Windows version of root. Same as on Linux. It's not
not really possible using cygwin.

> --
> Larry

__
Regards,

LL

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

  reply	other threads:[~2012-08-16  7:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15  2:09 Lord Laraby
2012-08-15  4:10 ` Lord Laraby
2012-08-15  9:35 ` Adam Dinwoodie
2012-08-15 10:56   ` Lord Laraby
2012-08-16  4:05     ` Larry Hall (Cygwin)
2012-08-16  8:51       ` Lord Laraby [this message]
2012-08-16 10:31         ` Corinna Vinschen
2012-08-16 12:02           ` Lord Laraby
2012-08-16 12:27             ` Corinna Vinschen
2012-08-16 14:04               ` Lord Laraby
2012-08-16 16:03                 ` Corinna Vinschen
2012-08-16 16:03                   ` Lord Laraby
2012-08-16 18:23                     ` Kurt Franke
2012-08-16 18:32                     ` Corinna Vinschen
2012-08-16 19:26               ` Christian Franke
2012-08-16 19:52                 ` Lord Laraby
2012-08-16 21:31                   ` Lord Laraby
2012-08-16 22:16                     ` Lord Laraby
2012-08-17  1:57                       ` Christopher Faylor
2012-08-16 22:46                   ` Linda Walsh
2012-08-16  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='CAG9p0OS3HKvaE9ye6g3vKP4kXPZGBw=uc-ELb0WcvdPefGQmFg@mail.gmail.com' \
    --to=lord.laraby@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).