Search results

  1. G

    Disable Exposure of the PHP Code for any user

    Now I’m having problem with BCompiler, when I use BCompiler in my application it always looks the file as it was in my project. for example if it was in C:\wamp\www\project when I compile and run it, and then after the Exe is done, I rename my project folder, it says: Warning...
  2. G

    Disable Exposure of the PHP Code for any user

    That’s not really a solution, is it? because it’s somewhere. but I guess that’s not much to do, although if you combine the obfuscation with http://www.fopo.com.ar/ with the BCOmpiler it generates a file that is very hard to bring the code back. Because BCompiler only deals with values...
  3. G

    Disable Exposure of the PHP Code for any user

    Ok If I activate bcompiler in the project , it works , but we can still see the name of functions and the functions we are using so they could rebuild the code. And how using absolute path for a folder would make it more secure? It doesn’t help at all, I tested. you can still see a lot of string...
  4. G

    Disable Exposure of the PHP Code for any user

    well there’s a easy way to view the code, even though it was marked with bCompiler in the project build, to start with the ExeOutput application built has total access to the Data Folder so all you need is to add a html file chooser then select any of the files of your code inside the Data...
Back
Top