Re: Thwarting classdump, etc.
Re: Thwarting classdump, etc.
- Subject: Re: Thwarting classdump, etc.
- From: Annard Brouwer <email@hidden>
- Date: Thu, 30 Jun 2005 09:48:56 +0200
On 30 Jun 2005, at 04:23, Bob Ippolito wrote:
On Jun 29, 2005, at 11:01 AM, Annard Brouwer wrote:
In one project we chose to do the "sensitive work" in C and the
rest in Java. If you choose to use this hybrid route that may be
the best trade-off...
That sounds silly, the mindshare that C has among people with
reverse engineering experience probably makes C code MORE likely to
be picked apart, not less.
There were other advantages to using C for that part of the code, I
know it would have been silly to do this just for "protection" even
though I may have implied that (thereby contradicting with what I
wrote earlier).
However, the main difference between Java and C is that for the
former you can throw your code at a decompiler and you're done. And
it's great! I've used this many times to fix bugs in other libraries.
With C, especially when you build it without symbols, it takes more
time to do this... But I agree with you that it is possible to pick
it apart.
Annard
_______________________________________________
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