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:from:to:subject:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=don
	Jj/u2hJgsmGSVTSgtonKn6lt1qe1nAILNuEJmuAgv2lrbNLNJ6MT7W8V3PaSfmDU
	tE3JTb6WYlBTADtdHRqocUNV457eFBu6EG5gPSx0hxhrJEPUdmjMH10m6Dme1gat
	CPTLLNK5qqhl+KOC/7GolF3xPpKDSUlKN5tSviK8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <E29840B52F804D728672875F0A8D534E@TKsamsung>
From: "Tony Kelman" <kelman AT berkeley DOT edu>
To: <cygwin AT cygwin DOT com>
Subject: Re: Compiled executables requiring admin rights - different results between MinGW host type
Date: Wed, 12 Mar 2014 11:00:07 -0700
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="iso-8859-1";	reply-type=original
Content-Transfer-Encoding: 7bit

> You won't believe it, but yes!  Welcome to the wonderful world of
> UAC installer detection!!!1!11

I get the impression you've been frustrated by this one before...

> See http://msdn.microsoft.com/en-us/library/bb530410.aspx
> and scroll down to the section called "Installer Detection".
> 
> I'll wait while you read...
> 
> [..."whistling while you work"...]
> 
> Finished?  Fine.  So, the only fault of your application is it's name.
> It's called "something-with-patch-in-it".  As everybody knows, an
> application which is called "something-with-patch-in-it" is an
> installer and needs elevation.  But only if it's a 32 bit application.

Wow. Thank you tremendously for this explanation Corinna. How bizarre.

> - Take one of the manifest files you find in Cygwin's /usr/bin dir,
>   and copy it alongside your binary, for instance:
> 
>     $ cp /usr/bin/patch.exe.manifest ./stringpatch.exe.manifest

That did the trick. In 64 bit Cygwin the only .manifest file I found in
/usr/bin was install-info.exe.manifest (apparently from texinfo package),
but that worked. Makes sense that 64 bit Cygwin wouldn't need as
many of these, but my primary use case where I'm running into this
issue is cross-compiling from 64 bit Cygwin to i686-w64-mingw32.

> - Wait until the next binutils version is released (should be in the
>   next couple of days), and link your executable with the new linker.
>   This will give you a default manifest integrated in your executable
>   by default, which doesn't only claim compatibility with all existing
>   WIndows versions, but also sets the RequestedExecutionLevel to
>   "asInvoker", which avoids the elevation for this executable entirely.

Don't the various MinGW cross compilers have their own binutils? I look
forward to this being the most convenient long-term solution, (renaming
could also work, but that pull request is going to result in some confused
looks and/or raised eyebrows) but will this need to come from upstream
(MinGW.org for i686-pc, or MinGW-w64 for i686-w64) to change the default
no-manifest-file behavior for any of the hosts besides 32 bit Cygwin?

-Tony


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