Quote: |
1- Is the above file only encrypted readable php code..?
2- Is the abode file first compiled into bytecode and then encrypted..?
2- Is the loader first decrypting the encoded file..? |
You'd better ask ioncube engineers about how their encoded file is produced.
In case of nucoder the answers would be:
Quote: |
1- Is the above file only encrypted readable php code..? |
encrypted with aes128
Quote: |
2- Is the abode file first compiled into bytecode and then encrypted..? |
right
Quote: |
2- Is the loader first decrypting the encoded file..? |
right
In general, there are only two types of php encoders and I wrote about it before
road-map-t4404.html?highlight=protection
If we talk about encoders in-general (in opposite to "packers"), the answers are provided below:
Quote: |
4- Once decrypted, is the file parsed and compiled again by php or is php told not to compile it because it is already compiled bytecode..? |
latter. Bytecodes go stright to the executor. Compilation phase is bypassed.
Quote: |
5- Is there any way to have a look at the bytecode of an encoded file..? |
With debugger everything that can be executed, can also be hooked/trapped. Absolute protection is a myth. But it does not mean that it will be easy to re-produce the original php sources even though the opcodes are hooked.