Re: executable obfuscator?
Re: executable obfuscator?
- Subject: Re: executable obfuscator?
- From: leenoori <email@hidden>
- Date: Sun, 10 Dec 2006 22:28:02 +0100
El 10/12/2006, a las 21:52, Andy O'Meara escribió:
Steve, assuming you're willing expend a level that yields a pretty
high bang for the buck, below is some simple stuff that our company
does. Our software targets both Mac OS and Windows, so the stuff
that we do has to be maintenance free as well as cross-platform.
The big picture is block entry-level crackers, and as Steve pointed
out, you'll never be able to stop determined blackbelt crackers.
To us, this is a winning strategy since entry-level crackers are
typically teenager-types that give up if it's not an easy crack.
The blackbelts are professional software guys by day and are
considerably fewer in numbers (so you have to have a big big
product to get their attention). By definition, the blackbelt's
time is worth money, so as long as you make it a PITA for them and
your title isn't a must-have, they'll move on to something else.
Couldn't agree with you more on that.
(a) Lightly encrypt "telltale" strings (and decrypt them on demand)
so that a cracker looking at the app's string table can't go any
useful leads.
I thought about this, but decided against it due to the fact that it
made working with localizations more cumbersome. How do you handle
the issue of localization, Andy?
In general, think back in your life on some of the most difficult
bugs that you had to find that led to inconsistent instability
(race conditions, memory smashing, double deletion, uninitialized
data). All you need to do is replicate that and you'll drive
crackers nuts and they'll move on to something else.
Hehe. I like it.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden