![]() ![]() And my knowledge is that ionCube is more secure. It is not the compilation that is the issue, is the security added before compiling. Zend is the most secure IMHO since it does not use PHP to decode and run your files like IonCube, but instead compiles it.They both work by compiling the code and both use a zend extension module to do the execution. It is the encoding bit which is important as that adds extra security to help reduce the usefulness of the output from a decompilation task.įor example the new Zend Encoder has function obfuscation and ionCube are releasing a new version soon with extra security (they haven't revealed what yet). Decompiling a compiled PHP file is aparrantly possible, but you don't get the formatting or comments since they're removed. There are services (or service since I've only and confirmed one) that can decode any encoded file for a small price. Incarcat de Accesari 1109 Data 30.10.10 Marime 5.1 MB Browserul tau nu suporta HTML5. ![]() You would still not be able to access class or function definitions though which makes 'decoding' pointless. I think it is possible to trace it in some way (like the linux binaries can be traced with trace utility) which would show what is it doing and you might be able to recreate some of that. It is not possible to simply decode such script. In this compilation many things are lost. My understanding is that Zend encoder does not encode scripts but rather it compiles them into code that can be executed by Zend optimizer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |