Re: Development workflows for signed code?
Re: Development workflows for signed code?
- Subject: Re: Development workflows for signed code?
- From: "Chris Suter" <email@hidden>
- Date: Tue, 9 Dec 2008 14:36:16 +0000
On Tue, Dec 9, 2008 at 4:12 AM, Jack Repenning <email@hidden> wrote:
> My experiments so far seem to show that none of those things happens. In
> fact, even if I modify one of the files, so that "codesign -v" no longer
> likes the bundle, it still seems to work. Is "codesign -v" the only
> (Leopard) thing that cares about all this?
My understanding is that the main thing that it affects at the moment
is access to the Keychain. If you break the signature, I think users
will be prompted to enter their password whenever they access the
Keychain. There are also implications for when upgraded applications
try and access the Keychain. The other thing that it affects is the
parental controls but I don't know the details. You can change the
behaviour of your application by using the Kill flag (IIRC) which will
prevent the application from running with an invalid signature.
It wouldn't surprise me if future releases of OS X make more use of
the code signature.
By the way, you should post code signing questions to the apple-cdsa
list rather than the Cocoa list as you'll get a better response there.
-- Chris
_______________________________________________
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