From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28948 invoked by alias); 12 May 2014 13:01:38 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 28930 invoked by uid 89); 12 May 2014 13:01:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: mail6.worldispnetwork.com Received: from Unknown (HELO mail6.worldispnetwork.com) (74.50.84.133) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 12 May 2014 13:01:32 +0000 Received: (qmail 18913 invoked by uid 399); 12 May 2014 13:01:31 -0000 Received: from unknown (HELO ?0.0.0.0?) (career@shaddybaddah.name@121.211.112.145) by mail6.worldispnetwork.com with ESMTPAM; 12 May 2014 13:01:31 -0000 Message-ID: <5370C60B.6080304@shaddybaddah.name> Date: Mon, 12 May 2014 13:15:00 -0000 From: Shaddy Baddah User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Icedove/24.4.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Baffled: is it Cygwin (64-bits) or Windows that causes the invocation of regedit (from bash) to fail? References: <849f1f5420ebf77d7a591d6c9b6bfa4b.squirrel@webmail.xs4all.nl> <536E339A.6030200@breisch.org> <6f9d939cc604437def11828435a67f96.squirrel@webmail.xs4all.nl> <20140512125054.GC2436@calimero.vinschen.de> In-Reply-To: <20140512125054.GC2436@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00217.txt.bz2 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