Vista & coreutils (or any other package)

Corinna Vinschen corinna-cygwin@cygwin.com
Fri Dec 15 22:33:00 GMT 2006


On Dec 15 21:53, Corinna Vinschen wrote:
> On Dec 15 09:20, Eric Blake wrote:
> > According to Corinna Vinschen on 12/14/2006 8:26 AM:
> > > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1020271&SiteID=1&mode=1
> > 
> > Oh. My.  Well, as I maintain coreutils, and don't have access to Vista, I
> > will have a very tough time testing any "workarounds" to this blatant bug.
> >  Deciding that a file is a "security risk" purely on its metadata is
> > absolutely wrong - it is the contents that matter, and not the file name.
> [...]
> Create a text file "install.manifest" with this content
> 
> === SNIP ===
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
>   <assemblyIdentity version="1.0.0.0"
>      processorArchitecture="X86"
>      name="install.exe"
>      type="win32"/>
> 
>   <!-- Identify the application security requirements. -->
>   <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
>     <security>
>       <requestedPrivileges>
>         <requestedExecutionLevel
>           level="asInvoker"
>           uiAccess="false"/>
>         </requestedPrivileges>
>        </security>
>   </trustInfo>
> </assembly>
> === SNAP ===

Stop right here.  In the aforementioned thread I got a very helpful
hint.  Just take the above text file and copy it to
"/usr/bin/install.exe.manifest".  That's it!  I had to touch
install.exe to circumvent caching, but afterwards it just worked.

I still think that the installer recognition is a bug in the UAC
design, but at least it's very simple to workaround.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list