On 12/14/06, Brian Dessent wrote:
Shankar Unni wrote:
> > The manifest route is pretty simple, you just create an .xml file, then
> > refer to it in a resource file, and then windres does the rest.
>
> But in cases like this, we really *don't* want to run with elevated
> privileges - if I'm "install"ing to /tmp, I definitely don't want to
> raise my privileges needlessly and potentially set up a security risk
> somewhere. (Admittedly this is an unlikely scenario, but...)
I thought the idea here was that the manifest tells the system
explicitly "I am not an installer and I do not need to be run with
elevated privileges", i.e. treat it like a normal program.
From Microsoft Vista's UAC Dev Requirements
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
When developing new installation programs, much like developing
programs for Windows Vista, be sure to embed an application manifest
with an appropriate requestedExecutionLevel element. See the Step Six:
Create and Embed an Application Manifest with Your Application section
for more information. When the requestedExecutionLevel is present in
the embedded application manifest, it overrides Installer Detection.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
So if you use
<requestedExecutionLevel
level="asInvoker" />
It should work without requiring elevated privileges. Maybe.
--
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/
