Hi there, I'm having a bit of an issue with one of my applications. The way the application works is by spawning a background process at app startup, the executable for which is contained within its Resources directory. While running, however, running `codesign -v xxxxx` on the PID of the background process returns:
xxxxx: code identity has been invalidated The signature of the main application validates just fine, and the signature of the background executable itself (while not running) is also valid. When running, however, it claims that its identity is no longer valid. A few things to take into account: a) The background process is a command-line tool (and thus has an inferred identity rather than explicit), while the main process is an app bundle. b) The background process calls NSApplicationLoad() (I don't know if it's relevant, but I can see how that could conceivably do something wonky to invalidate an identity). c) The background process loads Cocoa plug-ins (using NSBundle -load) from its parent app's PlugIns directory; so, however, does the parent app, and its signature does not get invalidated. Any thoughts on where I should look for problems and what I could do to prevent this invalidation would be much appreciated! -Matt_______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
