Re: plugins and permissions
Re: plugins and permissions
- Subject: Re: plugins and permissions
- From: Karl Kuehn <email@hidden>
- Date: Thu, 11 Dec 2008 15:40:57 -0800
On Dec 11, 2008, at 2:04 PM, Iceberg-Dev 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.
I do get that the only portion of the install routine that
Installer.app is elevating is the actual "install" phase, but think
that that is a bit silly. I guess I will have to file an "enhancement
request" with Apple on this point.
And I can't actually modify where the plugin is saving things, since
it is not really my plugin. I am raiding it from another installer to
take care of a system imaging hole. But thanks for the responce.
--
Karl Kuehn
email@hidden
_______________________________________________
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