Re: Code Signing for Mac application
Re: Code Signing for Mac application
- Subject: Re: Code Signing for Mac application
- From: "Paul Sanders" <email@hidden>
- Date: Tue, 16 Feb 2010 19:42:17 -0000
1. We use more than just a simple if statement (of course!) The
point about using code signing for anti-tampering checks is that
a code signature cannot be forged. We now use our own,
RSA-based scheme instead.
2. Someone tampering with my app (to sell it on some Russian
'OEM' software site, typically) does not have access to codesign
on the user's machine. Of course, because packages are forced
to install as root, they could hack my package and make it
install their own version of codesign... Erk!
3. We do not desire to make any post-deployment changes to our
app. Or if we do, we do it outside the Resources folder.
Something (ok, cause unknown) made unwanted changes for us :(
As I say, it was a painful experience. My reason for posting is
to try and save others some grief. And maybe Apple will get
stuck in and sort this out properly. It seems to have been left
on the sidelines.
Paul Sanders.
----- Original Message -----
From: "Graham Lee" <email@hidden>
To: "Paul Sanders" <email@hidden>
Cc: "Chris Espinosa" <email@hidden>; "XCode Users"
<email@hidden>
Sent: Tuesday, February 16, 2010 7:27 PM
Subject: Re: Code Signing for Mac application
It's true that code signing isn't compatible with
post-deployment
changes to the application, but it isn't really supposed to be
used
for an app's own anti-tampering checks either. If your app has
been
modified, the if(valid) jump might have been changed. Come to
that,
the codesign binary might have been modified.
Cheers,
Graham.
Graham Lee
http://thaesofereode.info
_______________________________________________
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