This is the mail archive of the
mailing list for the Cygwin project.
Re: Vista & coreutils (or any other package)
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="18.104.22.168"
> <!-- Identify the application security requirements. -->
> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
> === 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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html