dearnex
New member
An issue I’ve come across when using ExeOutput is security, how do you protect the vendor folder without having to compile it directly into your exe?
The reason for this question is: I’ve exported the vendor folder to Data and tried the encrypting option on compiling, however this causes Laravel to throw a wobbly because it doesn’t understand the contents of the php file.
Because of this I have been coaxed into adding the files to the exe itself increasing the size from 60mb to 130mb and increasing the load times from a couple of seconds to about 15 seconds. It’s not a life changing amount of time but it is enough to get on your nerves.
The main reason for this post is if you don’t encrypt the data/vendor folder it’s very easy for an unknown party to steal your source code with ease, even with all the protection turned on in the exe itself by simply going to, for example,
dumping the contents of every php file.
Is there a solution to secure this or is it best to keep it within the exe itself?
The reason for this question is: I’ve exported the vendor folder to Data and tried the encrypting option on compiling, however this causes Laravel to throw a wobbly because it doesn’t understand the contents of the php file.
Because of this I have been coaxed into adding the files to the exe itself increasing the size from 60mb to 130mb and increasing the load times from a couple of seconds to about 15 seconds. It’s not a life changing amount of time but it is enough to get on your nerves.
The main reason for this post is if you don’t encrypt the data/vendor folder it’s very easy for an unknown party to steal your source code with ease, even with all the protection turned on in the exe itself by simply going to, for example,
Illuminate\Routing\Controller and then in the callActiondumping the contents of every php file.
Code:
$files = scandir(base_path('app'));
foreach($files as $file) {
if (is_dir($file) === false) {
file_put_contents(storage_path(pathinfo($file, PATHINFO_FILENAME));
}