Code signing confusion
Code signing confusion
- Subject: Code signing confusion
- From: Jon Hodgson <email@hidden>
- Date: Wed, 24 Oct 2012 12:42:38 +0100
Hi,
I have a bunch of things that need signing, they include application
bundles, standalone binaries. plugins (components and VSTs) and
installer package bundles. These are for direct distribution, not the
app store.
Now generally speaking I'm finding the documentation hard to follow
because it doesn't seem to be clear exactly what I need in the way of
certificates and private keys, but my keychain currently has the
following..
3rd Party Mac Developer Applicstiion
- Mac App Submission
3rd Party Mac Developer Installer
- Chris Dev Key
Developer ID Installer
- Chris Dev Key
Mac Developer : Jonathan Hodgson
- Jonathan Hodgson
(I've abbreviated the above entries to save typing time, but hopefully
they show what's relevant).
All certificates show a green tick box when selected.
So, on to signing
If I try to use productsign on the installer packages with the "3rd
Party Mac Developer Installer" certificate it tells me I need to use
an application key because it's a bundle package, so try the same
thing with "3rd Party Mac Applicstion" and it seems to work fine,
check it with spctl and it seems to pass... so far so good.
But with codesign things seem different. Codesign runs seemingly just
fine, on both application bundles and individual binaries, and if I
use codesign's own verify option it tells me it is both "valid on
disk" and "satisfies its designated requirement"
However if I check the result with spctl it's rejected every time, and
if I ask for verbose out put I get
rejected
source=No Matching Rule
That's it! Doesn't seem very verbose to me.
I've tried various things with the app bundles, like specifying
specific rules, and removing the resources folder (in case something
in there was the issue), but I get the same thing with a simple
console app binary too anyway.
I have to do all my signing from the command line because although I'm
doing this testing in Mountain Lion my development is actually still
in Snow Leopard.
my guess is I'm missing something simple, but I'm hoping someone here
can give me a clue.
regards
Jon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden