Quote:
Originally Posted by LoRd_MuldeR
"Protecting" your code only makes sense if you either...
(1) plan to sell your software commercially
(2) need to hide your algorithms from your antagonist (e.g. decryption software)
(3) want to hide malware in your software
In case (1) you could simply buy a license for one of the commercial executable protectors/obfuscators (e.g. ASProtect).
That still won't give a "safe" protection, of course. But I'm sure it will be at least as hard to crack as your own protection. And it saves you trouble/work.
Also since many (commercial) applications are protected with such tools, the chance that any A/V software will complain is very low.
Case (2) certainly doesn't apply to a H.264 decoder, so I have to speculate that we have a case (3) here...
|
IMHO, commercial executable protectors/obfuscators what you recommend is bad. Themida is pretty good, but I have seen many themida-protected examples are cracked. The commercial protectors are researched deeply and a experieced cracker can crack it very easily. I am very familar with many kinds of anti-debug skills, so I do it myself and I can integrated it into the DiAVC closely. Then I protect some critical functions using the VMProtect.
I never hide some malwares in the DiAVC, I have engaged in the software for several months and I want to sell it online in future, I will never risk my business.