Re: OCTET_STRING_t -> NSString?
Re: OCTET_STRING_t -> NSString?
- Subject: Re: OCTET_STRING_t -> NSString?
- From: Quincey Morris <email@hidden>
- Date: Tue, 29 Mar 2011 13:24:27 -0700
On Mar 29, 2011, at 13:03, Todd Heberlein wrote:
> I thought my Mac Cocoa program was pretty much done, and that all I needed to do was check off a box in Xcode's packaging or Apple's iTunes Connect web site saying "I want copy protection".
FWIW, my understanding of the reason it doesn't work that way is this:
A standard implementation of the receipt checking code could would permit a single hacking tool to hack away the protection from *every* Mac App Store download. If you implement this yourself, a hacker has to target your application specifically. Chances are, that won't be worth any hacker's time unless your app is incredibly successful.
As a consequence, once you have your code working, you should probably try to rearrange it a bit (reorder functions, obfuscate names, etc) to make it less like the sample code you're following along with, so that it's slightly more work for a hacker to crack your application. A hacker who have to spend a couple of hours at it, rather than a couple of minutes, might just not bother, and move on to some other unfortunate target.
As I said, FWIW.
_______________________________________________
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