Re: OCTET_STRING_t -> NSString?
Re: OCTET_STRING_t -> NSString?
- Subject: Re: OCTET_STRING_t -> NSString?
- From: Todd Heberlein <email@hidden>
- Date: Tue, 29 Mar 2011 13:39:57 -0700
On Mar 29, 2011, at 1:24 PM, Quincey Morris wrote:
> FWIW, my understanding of the reason it doesn't work that way is this:
> ...
That is pretty much what the Apple documentation says. I felt that they were saying, "This is left as an exercise for the reader." :)
The hacker community has had automated obfuscation tools for years. Some worms implement this internally so each new instance is different than the previous one. In these cases, instead of avoiding a hacker who wants to break copy protection, they want to prevent AntiVirus vendors from coming up with a signature to detect the malware.
It seems that a great service to the Mac programming community would be to repurpose one of these tools to randomly obfuscate a base receipt validation code base and produce source code you can paste into your program. Then each person gets a unique version but doesn't have to code it themselves.
Maybe after I get version 1.1 of my software released I will take a look at this.
Todd
_______________________________________________
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