Re: Thwarting classdump, etc.
Re: Thwarting classdump, etc.
- Subject: Re: Thwarting classdump, etc.
- From: Annard Brouwer <email@hidden>
- Date: Wed, 29 Jun 2005 23:01:54 +0200
Hi Dave,
If your project would really attract the wrong people to "break in"
your code, there's nothing you can do about it. Other than doing a
sophisticated checksum over the binaries and hide that value in
multiple places in your code somewhere to see if it has been tampered
with. Determined people will get into your code no matter what. Since
the system is able to run it, they can do it. There were many heated
discussions about this in the Java camp. But also look at games and
other programs that try to prevent people from cracking it (in vain).
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...
Annard
On 29 Jun 2005, at 22:40, Dave Hersey wrote:
This isn't just paranoia--I have a project in mind that needs a
very high
level of protection against anyone "rewiring" some user code that
interacts
with a kext. And, there *are* illicit reasons why they'd want to.
As much as
I'd like to write it in Cocoa, I'm really wondering if that makes
the most
sense because of security issues.
_______________________________________________
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