• 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: Richard Somers <email@hidden>
  • Date: Mon, 30 Nov 2009 11:05:43 -0700

On Nov 30, 2009, at 10:23 AM, Matt Neuburg wrote:

If the app is code-signed, it will not run when the executable is altered.


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.

--Richard

_______________________________________________

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


  • Follow-Ups:
    • Re: Hiding String Constant in Compiled Code
      • From: Rob Keniger <email@hidden>
References: 
 >Re: Hiding String Constant in Compiled Code (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: Hiding String Constant in Compiled Code
  • Next by Date: removing all sublayers from a layer with fast enumeration
  • Previous by thread: Re: Hiding String Constant in Compiled Code
  • Next by thread: Re: Hiding String Constant in Compiled Code
  • Index(es):
    • Date
    • Thread