If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Hybrid View

Reverse engineering software protection

I am looking for a solution to protect software from reverse engineering.
Has anyone seen a good multi-platform solutions?
The only thing that I could find, is code obfuscation software http://morpher.com/
Does someone have experience with this solution?

I am looking for a solution to protect software from reverse engineering.
Has anyone seen a good multi-platform solutions?
The only thing that I could find, is code obfuscation software http://morpher.com/
Does someone have experience with this solution?

This is definitely interesting question.

As it was mentioned before, there is no absolute protection against the reverse engineering. Everything can be broken provided enough time and resources. However, in practice many tradeoffs are involved. If your algorithm / app costs, say, $15 and the protection is strong enough then you will be more or less safe (unless your app will be caught by some fanatic which will do the pretty expensive protection removal procedure 'just for fun').

On the market you can find many solution which provides some sort of "envelope" around your binary. They are fine, when you need to protect "just the app" (thus they are extremely popular across shareware makers and that's why they are moderately cheap), but definitely not suitable when you have some proprietary algorithms you want to hide since your algorithm appears in its original form after (even partial!) envelope removal.

The situation with more sophisticated tools are not so good. There are not so many players in such a market. The reason is quite simple: making such tool usually as hard as making a decent compiler itself (almost all tools here are in fact compilers!). Sich a compiler can use much more information about your program and thus can perform sophisticated high-level transformations which are simple not available when your program is already translated into the final binary form.

As you mentioned, another question is multi platforms. Envelope-like tools operate on the final binary and thus must be made for every new platform. So, basically, they should be written from scratch. And you end with 10 different tools for every platform you want to support. Compiler-like tools are in the better situation, since they can perform the necessary transformation regardless of the trarget platform. Only the final codegeneration should be changed and this can be considred as a "standard compiler maker project".

So, returning to "morpher.com" product - I think it does make sense asking them for conditions / trial version, etc. For me it seems that it is the single compiler-like solution (can someone correct me?) available for Windows, Linux and MacOS X at the same time and thus looks pretty promising.