Codesign additional items within an app bundle
Codesign additional items within an app bundle
- Subject: Codesign additional items within an app bundle
- From: Michael Diehr <email@hidden>
- Date: Sun, 17 Oct 2010 07:53:51 -0700
Taking my first stab at codesigning an OS X App, and I'm noticing that only some items within the app bundle get signed, e.g.:
codesign -s 'My Company' /path/to/my/MyApp.app
seems to only sign some of the files in a bundle:
MyApp.app/
Contents/MacOS/MyApp (the executable)
Contents/Resources (resources)
In particular, it does *not* seems to notice or sign the files:
Contents/MacOS/xyz.dylib
Frameworks/*
(some of these are extra files and helper apps I'm putting in myself during the build process).
Documentation on this is confusing, and google isn't really helping.
It sounds as if stand-alone helper apps should be codesigned individually, which I can manager.
However, what about other information (data files and dylibs) that are not in the Resources folder?
Is there any way to tell codesign to "sign the entire bundle, including custom folders/files"?
I've looked at
codesign -R ResourceRules.plist
but I can't find any good documentation -- it seems like this is a way to Exclude files in the Resources folder, but I can't see how to use this to Include files that are outside the resources folder (e.g. if I wanted codesign to pay attention to files in MyApp.app/Contents/MyData/data.xxx )
I've looked at
codesign -r requirements
but I can't really understand this either -- it's not clear whether one can use requirements to say "sign these files too".
Any advice?
_______________________________________________
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