X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=G10FDnnWkKq9WldlLHTTfdBDE/xI2ShtlxMTEuOaQAW
	0UmYmFouGnNKWI3Hdu2fGkUsS7qwFwQFEBV4t965Ht4N3rpu8SvhnoOzV2JCnKPd
	UJsbU8G2VTkbHsixZIcEhFRld5RkwwirEVv/NjpU+VMf8VgsLV2PZ4voFqrANMJM
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=G7FjoF9qcmefQ4HkVTTx6yVzeyE=; b=dPfvCjVGwsyZX8DIk
	UuMfe1dpnPizSDeXLep22sFvO0A0i2a1ByNHdGoAWKctlQdj+QA0XuXu7ZDy3i4g
	sW5vtwbWs5LdK0qIxUT9uqCC6KQgtbRxNSTF1CJ3lPWBsJCxitMMBEEyb1n84oDT
	VVFhG0a0GcL7XybEHOzME1u918=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_40,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,SPF_PASS autolearn=ham version=3.3.1
Message-ID:	<51EFD0EB.6030804@cwilson.fastmail.fm>
Date:	Wed, 24 Jul 2013 09:04:43 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version:	1.0
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: setup-x86_64: postinstall errors: Package bash 1, Package a2ps 2 and xinit 134
References:	<CADex0xx+uY6Y8ngZ3tUsYr+KPi0t0+H+H7X-civ-iq0diuJfZw AT mail DOT gmail DOT com> <51EE0951 DOT 90007 AT users DOT sourceforge DOT net> <51EEC7F2 DOT 5000402 AT cwilson DOT fastmail DOT fm> <20130723184615 DOT GK9689 AT calimero DOT vinschen DOT de> <51EED4B4 DOT 7000908 AT cwilson DOT fastmail DOT fm> <20130723192342 DOT GM9689 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20130723192342.GM9689@calimero.vinschen.de>

On 7/23/2013 3:23 PM, Corinna Vinschen wrote:
> On Jul 23 15:08, Charles Wilson wrote:
>> But even if /bin/bash is elevated, it doesn't follow that any of the
>> tools launched within a script -- via cygwin's fork/exec method --
>> ALSO retain that elevation.
>>
>> Does it?
>
> Yes, it does.  CreateProcess propagates its own user token untouched.
>
> Weird question.  Did you ever start an elevated shell and lost your
> admin permissions in a child process?  If that would occur, nothing
> would work right in an admin shell.  Even the `id' call would not show
> the admins group in your supplementary group list.

OK. At one point I thought there was an issue with propagating 
elevation, but I guess not.

So...is it possible to launch setup*.exe in an UNelevated context 
(somehow bypassing the UAC detection, even though we don't ship a 
manifest)?  Then, if the user selects 'Install for All Users' you would 
see this problem.

--
Chuck



--
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

- Raw text -