From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: Re: Baffled: is it Cygwin (64-bits) or Windows that causes the invocation of regedit (from bash) to fail?
Date: Mon, 12 May 2014 13:15:00 -0000 [thread overview]
Message-ID: <5370C60B.6080304@shaddybaddah.name> (raw)
In-Reply-To: <20140512125054.GC2436@calimero.vinschen.de>
Hi,
On 2014-05-12 22:50+1000, Corinna Vinschen wrote:
> On May 12 14:20, Houder wrote:
>> Of course, it is not really a problem, that regedit cannot be invoked from Cygwin, as it can
>> be invoked from the Windows interface ...
>>
>> However, in some of the "harder" cases of using Gygwin, one needs to have a "mental" model of
>> how Cygwin "integrates" with Windows (is my belief) ... and as far I understand the matter, I
>> was surprised to find that I could not invoke regedit from bash.
>>
>> Consequently, I decided to investigate why I got the denial (64-bits Cygwin) at my end.
>>
>> First of all, some more info about my "environment":
>>
>> - I am using Cygwin from Windows 7 ...
>> - I am using Cygwin from an administrative account ...
>> - furthermore, using secpol.msc, I have set the ConsentPromptBehaviorAdmin field in
>>
>> HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System (key in registry)
>>
>> to zero, meaning 'elevate without prompting'
>
> Doesn't matter. The problem is that elevating is a special procedure,
> requiring a special form of ShellExecuteEx function, which doesn't
> integrate well with the requirements of POSIX fork/exec. Therefore
> Cygwin never calls ShellExecuteEx to fork/exec an application, rather it
> calls CreateProcess/CreateProcessAsUser, both of which don't provide a
> way to elevate a process. Therefore, to elevate a process from a Cygwin
> shell, the shell must already run elevated (e.g., right click on "Cygwin
> Terminal" -> "Run as Administrator...").
>
> What's really annoying: RegEdit's mainfest does not request "asAdmin"
> rights. Rather it only requests "MaximumAllowed". One would think this
> means that a CreateProcess call would simply continue with the current
> permissions of the user. Not so, unfortunately.
I am not sure which Edition it started in, but I believe regedit opens
as the invoking user from Windows 8.1 at least (perhaps 8, I have a
vague recollection).
--
Regards,
Shaddy
--
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
next prev parent reply other threads:[~2014-05-12 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 13:42 Houder
2014-05-10 14:11 ` Chris J. Breisch
2014-05-12 12:50 ` Houder
2014-05-12 12:51 ` Andrey Repin
2014-05-12 17:13 ` Houder
2014-05-12 13:01 ` Corinna Vinschen
2014-05-12 13:15 ` Shaddy Baddah [this message]
2014-05-12 13:23 ` Corinna Vinschen
2014-05-12 18:47 ` Houder
2014-05-12 17:31 ` Houder
2014-05-13 15:10 ` Houder
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=5370C60B.6080304@shaddybaddah.name \
--to=lithium-cygwin@shaddybaddah.name \
--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).