![]() You have to make sure the customer uploads the php files in BINARY mode, and also unzip them without using the automatic newline thing. This is really the only complaint I’ve been able to find regarding ionCube. Others: mostly source based techniques similar to codelock. Loader (Zend Optimiser) not obfuscated, and encoding techniques more easily exposed (contrast running strings on the ZO and ionCube binaries), but not necessarily a weakness and may not ultimately help a hacker. Highly secure, also uses optimised bytecodes and closed source execution engine. ![]() Uses optimised bytecodes, algorithms hidden with obfuscation technques in the Loader, closed source decoder and execution engine, custom bytecodes etc. IonCube: Actually never cracked, though Russian hackers did try (and gave up) in a 3rd party competition that we endorsed. SourceGuardian: Was easy, may be harder with their “byte code” encoding. Zend: Is possible, has not fully been cracked to the best of my knowledgeĬodelock: Yes, trivial to crack with a printf in compile_string() ![]() ![]() IonCube: Hard to crack but can and has been done
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |