|
A closed source most of the user don't like I think, there are many reasons why not, like the user don't know whats the web app doing (bad coding, open backdoors or whatever), whats happen when a new php/apache version coming out and what's with the performance, yes it's great that you used some well cache solutions in but on every request many times ioncube engine need to load the code, with 10 req/sec for sure no problem, try with 200 req/sec and more. Or whats happen if the vendor stop his business? and and and.....
Who tell you that Ioncube is not hacked? Official since November 2004 a easy way was found how to decode the source out from ioncube encoded source.
To decode this 223 files in the tar it takes not more then 15 min.
OK, you used the new feature of ionCube 6.5 to Obfuscate the Function and variable names of the code, this makes the reverse engineering harder, with some experience 10 hours later the reverse engineering is finished.
__________________
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
WTB: Video Dating Profiles ICQ: 8.21 / 000 (digits only)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
|