Re: Code Signing for Mac application
Re: Code Signing for Mac application
- Subject: Re: Code Signing for Mac application
- From: Graham Lee <email@hidden>
- Date: Tue, 16 Feb 2010 14:15:51 +0000
On 16 Feb 2010, at 14:07, Gabriele de Simone wrote:
> I was under the assumption that signing your code means that if the executable file or one of the non-localized resource files get modified, the OS would prevent the app from being run, and signal the user that something's wrong. Instead, I can insert random bits into the executable, modify the Info.plist or files in Resources without any warning at all. My app just runs as if Code Signing did nothing. Am I missing something big and obvious about how this technology works?
Yes - the code signature is only tested by certain facilities in the operating system. Currently the kernel doesn't care about the identity of code, it will launch signed, unsigned and invalid code alike (unlike the iPhone). Keychain Services, Parental Controls and the firewall all _do_ care about the code's identity, so your application won't play well with those facilities after you make the changes you describe. If you never make network connections or access the keychain, and never test against Parental Controls, you won't see any side-effects from bad code signatures.
Cheers,
Graham.
--
Graham Lee
http://blog.securemacprogramming.com/
Coming soon - Professional Cocoa Application Security
http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0470525959.html
_______________________________________________
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