added execute permission to start_services

[kimocoder]

• Added execute permission to start_services.sh to the tool doesn't halt when trying to execute it.

[Ekultek]

Why?

[kimocoder]

after running autosploit.py, the tool halt when trying to start the services (after postgres question) adding execute permission let autosploit go to console (starts like it should)

[Ekultek]

The tool doesn't hault when trying to start the services, it starts when the program begins. Adding the permissions for an executable does the same thing as doing sudo bash <FILE>.sh but reads from the shebang line.

[kimocoder]

tested it not long ago, but give me a moment I'll go check it again.

[Ekultek]

Do this:

cat << _EOF > test.sh #!/bin/bash echo "this is a test" _EOF bash test.sh && chmod +x test.sh && ./test.sh` 

The output will be:

this is a test this is a test 

The only difference is one is executable and one is not, see here:

-rwxr-xr-x 1 admin staff 22 Apr 3 12:17 test.sh -rw-r--r-- 1 admin staff 0 Apr 3 12:17 test1.sh 

[kimocoder]

Re-producing it all gives this

[Ekultek]

You have to run with sudo so we can see the process PIDs

[kimocoder]

running as Kali root, using sudo would give the same output

[Ekultek]

I'm gonna go ahead and test this really quick

[Ekultek]

that's pretty fucking cool, merging

[kimocoder]

Quick fix! thanks sir