site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com

Hi All,

I don't mean to beat a dead horse, but we are close to deciding what

to do when our preflight script finds wrong permissions or owner

when checking /Library/PrivilegedHelperTools/ and it's parents.

Here are the remaining questions we have boiled down to:

1.  Should we just aspire to the same degree of permissions/owner

repair that Disk Utility does, i.e., not care about the owner on

"/"?  BTW, DU does not fix a bad owner or permissions of

/Library/PrivilegedHelperTools/.  I know some of you have said that

DU should fix the owner of "/".

2.  If the user's system already has permissions/owner settings that

are insecure, are we creating any additional insecurity by

installing a daemon into a structure that is already compromised?

Do we have a responsibility, as a third-party software installer, to

fix this situation?

Thanks for your input.  We will make our decision this evening, Pacific time.

Regards,

Monte Benaresh

PACE Anti-Piracy

Another thing I just noticed.  Failure during pre-flight script is not supported by Installer.  You need a Volume Check or Installation Check if you want to support installation failures based on scripting.  Can't find the thread with that in it yet, but it was an old post of mine where I was told it's not supported.  <- only link i could find to the old post, given your decision deadline.