This is the mail archive of the
mailing list for the Cygwin project.
Re: setup-x86_64: postinstall errors: Package bash 1, Package a2ps 2 and xinit 134
- From: Andrey Repin <anrdaemon at freemail dot ru>
- To: Charles Wilson <cygwin at cwilson dot fastmail dot fm>, cygwin at cygwin dot com
- Date: Wed, 24 Jul 2013 17:34:06 +0400
- 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> <51EFD0EB dot 6030804 at cwilson dot fastmail dot fm>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Charles Wilson!
>>> 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
Yes, is you rename it to something less apparent. People suggested
> (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.
Andrey Repin (email@example.com) 24.07.2013, <17:33>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple