I would guess the domain option supersedes the authentication option as when you install items into the current user's home directory, root permissions are not needed. That's the design issue of this domain/installation destination option: it affects all the packages within a distribution. There's no way to install packages both in / and ~ with this option. On Wed, Aug 22, 2012 at 2:44 PM, Harald Dersch <Harald.Dersch@vasco.com> wrote:
I'm afraid you're right. I prepared a package without using domains by installing to the user folder via the 'tmp folder hack'. This is awful, but it works. The script runs as root, the executable has administrative privileges and works correctly. I wonder why it's called root/admin authentication, then.
Thanks,
Subject: Re: Run flat package postscript as root From: Stephane Sudre <email@hidden> Date: Wed, 22 Aug 2012 12:18:28 +0200 Authentication-results: symauth.service.identifier Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=18iyTVYnaIeRCWQWkRj5eSpFQ77kr+o0tw1m5EPxiac=; b=VzOboSVDdg5B4JB5UqaTllToUWYpI6+sYaWUSOX/b7PS414a960JnY770zmENYxXZt CDbfwDHFCi8jEPNnWoLaY8pkyzUE7jjGgyO3jIruJdCa/Y9cpF/HMmMmW9hxz8OPqFLv >BUL+8rx9gXgk8CXdLhQIXJSZBv7Om7kHfGleKSmqrVfAU/9X80bLICF73JL+BJe0P2BO RAp4BcXqUKJvv8Vxr0JabqoNuapYQcuv0Q6+Rl9CVpWCyEHp016bv4JpY6P6Lhv1rzk+ >Y5mK8c+b10fj+ObYi98wg0DOGq2bRQI0HK7nuNwNFPOdod+ho4No3e1H2+GmFU+bwDZ9 2ySg==
It's probably related to the use of the "current user/user home directory" domain/install Destination.
On Wed, Aug 22, 2012 at 9:44 AM, Harald Dersch <email@hidden> wrote:
Hello, I'm currently developing a setup targeting flat packages. The setup installs a browser plug-in to the user home folder (via current user domain), but needs to change a global registration. The registration is done by an executable included as an additional resource in the setup and supposed to be launched by the postinstallation script.
I did a project with one package where I enabled "Require admin password for installation". I get a credential prompt, and the plug-in is correctly installed to the current user folder. However, postinstallation is not executed as root, no matter which credentials I provide, hence the executable fails. If I try to launch the executable explicitly using sudo, I get "sudo: no tty present and no askpass program specified" (in the log).
It doesn't matter, if I use PackageMaker or sudre's Packages.
From the Packages user manual (Section "Defining a package pre- and post-installation scripts"): " >> If the installation process requests an admin password, the pre- and post-installation scripts will be run as root." -> Obviously this is wrong, or do I miss something?
Thanks for any input, Harry
_______________________________________________ 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
-- Packaging Resources - http://s.sudre.free.fr/Packaging.html
_______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/dev.iceberg%40gmail.co...
This email sent to dev.iceberg@gmail.com
-- Packaging Resources - http://s.sudre.free.fr/Packaging.html _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com