Code Signing for Mountain Lion
Code Signing for Mountain Lion
- Subject: Code Signing for Mountain Lion
- From: Pascal Harris <email@hidden>
- Date: Sun, 02 Sep 2012 20:09:02 +0100
I'm just updating one of my more useful little tools (Locamatic) so that it is code signed for Mountain Lion. I know in advance that this program won't be suitable for the app store, firstly because it's a Preference Pane and secondly because it schedules shell scripts (packaged within the pref pane) to execute when certain conditions are met (gateway changes). I'd like to code sign it so that users can download it from my website and use it without breaching the default gatekeeper configuration though.
I have two questions regarding this:
1. Do the internal shell scripts have to be signed separately (and as a corollary, can shell scripts be signed)?
2. When I sign the preference pane (using codesign) everything appears to be successful. When I verify with codesign, it returns nothing (which I understand to be a good thing). However, when I then download my finished prefpane to my test vm, also with Mountain Lion, it fails to pass GateKeeper (can't be opened because it is from an unidentified developer). What am I doing wrong?
Thanks as always, and regards,
Pascal
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden