Re: Permissions checks when installing a daemon
Re: Permissions checks when installing a daemon
- Subject: Re: Permissions checks when installing a daemon
- From: Stephane Sudre <email@hidden>
- Date: Mon, 16 Aug 2010 16:39:18 +0200
On Sat, Aug 14, 2010 at 2:37 AM, Monte Benaresh <email@hidden> wrote:
>
> Hello All,
>
> One of our installers installs a daemon to /Library/PrivilegedHelperTools/. I have written a bash script to enforce the security recommendations in TN2083, which says that this directory, and all of its parents, must have certain permissions and must be owned by "root" in order to prevent an unauthorized process from substituting their own daemon in place of ours.
>
> Our problem is, one of our Beta users has "/" owned by "_spotlight", and so we fail to
> install due to the security checks in our preflight script as alluded to above. Disk Utility does not repair this problem.
>
> We are concerned that this will be a support issue, so our questions are:
>
> 1. Can we securely allow "/" to be owned by other than "root"?
No.
> 2. Is it permissible for us to change the owner of "/" to "root"?
> 3. If either /Library/ or Library/PrivilegedHelperTools/ is not owned by "root" is it
> permissible for us to change the owner to "root"?
This could be done either using the Overwrite directory permissions
flag or through a postinstall script.
The problem you may need to consider is that by reverting the owner to
root, you may enable some unwanted (bad) process to run.
_______________________________________________
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