Re: plugins and permissions
Re: plugins and permissions
- Subject: Re: plugins and permissions
- From: Iceberg-Dev <email@hidden>
- Date: Thu, 11 Dec 2008 23:04:40 +0100
On Dec 11, 2008, at 7:34 PM, Karl Kuehn wrote:
I am trying to wrap a re-written installer plugin (the licensing
module for Final Cut Pro) in my own installer for internal use. But
it needs to touch a file in a restricted space on the hard drive.
The problem I am having is that no matter what requirements I put
on the package (admin/root permissions) the plugin always seems to
be run as the installing user rather than with elevated privileges.
I have a rough work-around in place in running the plugin after the
install phase runs with a script to pave the way, but this leaves
the permissions in a state I am not completely happy with.
I am using Iceberg to make my packages (can't seem to figure out
how to do plugins in PackageMaker... didn't try long), and I have
tried digging around the original installer to see if that is
packaged any differently, but I have not found anything.
Anyone have an insight for me?
Installer Plugins are plugins for Installer.app so they are run with
the current user permissions. A possible woraround is to have your
plugins save some data in a place where a postflight script (or
executable) could read it and do the job.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden