Thread: C Obfuscation / Encryption

Quote: Originally Posted by jwdonahue The trouble with this approach is that you may make it a little more difficult to reverse engineer, but you can't completely prevent reverse engineering. It sounds like what you really need is a good license manager, but there really isn't any such thing anywhere in the world. If you find something that does the trick, chances are it got used on more than one product and that made it a big...

Google software license protection . I think that the method of splitting up the algorithms into meaningless fragments and distributing those is the best way to go. Let them reverse engineer it. So what if you seem to be multiplying and then dividing something over and over and over again? It doesn't get give them your unique solution to the problem unless they hack a substantial fraction of your nodes in real-time. That raises the bar...

<offtopic> @scorpion The only place where I encountered self modifying code was in Haskell. You might not know whether a list might have strings, or numbers, or a list of numbers, but you can define for example concatenation operator, or define a completely new language, by making a parser, but even then I can still determine flow of the program ... I thought obfuscation would entail encryption and decryption, could have it pre...

You could use stuff like self modifying code if you really want to get down into to it. Not that it would help against a truly determined attacker, but at least it will slow them down.