I’m not certain this is a gatekeeper issue. You can always test that by building a distro package using the components internally, isolating the external architecture as a potential cause. Can you expand on why you need to house external components in this way? It seems like a lot of extra overhead, and there may be alternative solutions (like scripting the mounting, extraction, and execution of the external components). On Aug 6, 2013, at 3:20 AM, nestor pridun <nestor.pridun@native-instruments.de> wrote:
hi,
i think this question already came up a couple of times but did not receive an answer. so i just try again:
we are building distribution packages with references to external packages. these packages are deployed on disk images. we are using x-disc to reference the pkgs located on the disk images:
<pkg-ref id="someid" installKBytes="123" version="1.2.3" auth="Admin">x-disc://pkgname.pkg</pkg-ref>
the distribution package and all external packages are all signed with productsign and can be successfully checked using "pkgutil --check-signature". nevertheless when launching the installer the lock in the UI is not displayed and gatekeeper is invoked with the "Installer.pkg is damaged and cant be opened. You should eject the disk image" dialog.
is it possible to build and sign such a distribution package in way that gatekeeper is not invoked?
cheers, nestor. _______________________________________________ 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/conor%40mac.com
This email sent to conor@mac.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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com