Re: Thwarting classdump, etc.
Re: Thwarting classdump, etc.
- Subject: Re: Thwarting classdump, etc.
- From: Dave Hersey <email@hidden>
- Date: Tue, 28 Jun 2005 13:14:36 -0400
Thanks. I thought there were also ways with Objective C to register classes
at runtime, so that there was basically nothing useful to dump otherwise.
That's what I was originally looking for. Is anyone doing that?
- Dave
On 6/28/05 12:50 PM, "phil" <email@hidden> wrote:
> You can use some obfuscating technics, by instance renaming all your
> great class and message names by a known random renaming scheme and
> build your release target with those names. You can use script
> targets to obfuscate your source files before the build phase. (sed
> is your friend)
>
> What's about a xfgh124dkkslkqjpqroj35qsdlknlknlq012knglkqnglkngqlkqn
> $kjfnkjfnfkjnf__kjfnf_kjdfkfdj__ofdnkfdjnfdkjnfdkj: message selector?
>
> There's a long way to decode such classdump files and that's indeed a
> short name.
>
> An Apple's public framework can't use that bad thing, but your
> private application?
>
> Yours,
> --
> phildev
>
> On 28 juin 05, at 16:15, Dave Hersey wrote:
>
>> Does anyone know of a good resource that covers obscuring methods from
>> classdump and thwarting other approaches to reverse engineering a
>> Cocoa app?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden