• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Hiding String Constant in Compiled Code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hiding String Constant in Compiled Code


  • Subject: Re: Hiding String Constant in Compiled Code
  • From: Rob Keniger <email@hidden>
  • Date: Tue, 1 Dec 2009 12:16:09 +1000

On 01/12/2009, at 4:05 AM, Richard Somers wrote:

> I could be wrong but I do not think this is the case. The documentation states "Once you have signed your code, any change in the code that you did not intend—whether introduced accidently or by hackers—can be detected by the system." No where does it say the system will not run the altered code.


Launchd will terminate the application on launch if a change is detected, provided you sign the application with the -kill flag.

However, as Jens points out, this is not a solution.

--
Rob Keniger



_______________________________________________

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

References: 
 >Re: Hiding String Constant in Compiled Code (From: Matt Neuburg <email@hidden>)
 >Re: Hiding String Constant in Compiled Code (From: Richard Somers <email@hidden>)

  • Prev by Date: Re: NSAffineTransform scaleBy not scaling
  • Next by Date: Re: copyWithZone - if anyone could explain this to me ?
  • Previous by thread: Re: Hiding String Constant in Compiled Code
  • Next by thread: AudioToolbox Pitch Bend?
  • Index(es):
    • Date
    • Thread