Re: Gatekeeper and downloading packages
Re: Gatekeeper and downloading packages
- Subject: Re: Gatekeeper and downloading packages
- From: Stephane Sudre <email@hidden>
- Date: Wed, 20 Feb 2013 09:46:08 +0100
On Wed, Feb 20, 2013 at 8:00 AM, Natalia Antonova
<email@hidden> wrote:
> Hello
>
> My Distribution refers to component packages that are downloaded by a plugin
> later in the installation. Though both distribution (mpkg) and component
> packages are correctly signed, Gatekeeper assessment fails. I suspect
> Gatekeeper evaluates all the pieces right after user double clicks on the
> package, and if some part is not signed or is not there yet (my case) - the
> assessment fails.I am 95% sure this is a limitation we have to leave with,
> but perhaps someone knows a workaround (except creating an own installer)?
Yes, this is a limitation. Even when the certificates are the same for
the distribution and remote packages, it fails. I haven't found a way
to make it work either.
> Another question is what is the best place to store component packages
> downloaded by my plugin?
> I noticed that if Distribution contains http URL to packages, Installer
> keeps them in /tmp folder. But wouldn't it better to store them in
> "~/Downloads"? But I am not sure how to set this in Distribution file (and
> if it's really possible).
Not possible as far as I know. You can only provide the remote URL not
a local download folder. I assume the package is downloaded in the
same kind of /tmp "sandboxed" location used to expand the flat
packages.
_______________________________________________
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