-
Notifications
You must be signed in to change notification settings - Fork 1.1k
AutoSploit not executing msf commands in docker #1210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Are you saying that you have msf inside of a docker container and want to execute the commands in the container, or that the docker image with AS is bad? |
@NullArray we could just add a |
Correct, I'm trying to execute AutoSploit from a container without user input, using -e and -f arguments. |
@scmanjarrez what do you think of the docker flag idea above? Or do you think it would work better to detect if the user is inside a docker container and go from there? |
it's ok for me to use the --docker flag, right now I'm detecting if autosploit is running inside a docker container, but it would be better to make it general so it'll work regardless the container tool. |
Alright I’ll create a way to determine if we’re inside a rocker container, that should make it more portable instead of creating a flag that will have to be passed. Basically what I’ll do is just check if we’re inside a container, if we are, I’ll get it to run without sudo. It’ll be up to you to pass the path though (if needed) |
fixed via 03020fd look for it in the next merge |
Uh oh!
There was an error while loading. Please reload this page.
Running information
Exploit module information
Program information
I have run AutoSploit in docker and it isn't working correctly. You can see that exploiter.py is executing the command "sudo msfconsole ...". In the docker machine there is no "sudo", so it fails the execution, then, "msfconsole" is not in PATH so it won't work either.
After removal of "sudo"
and addition of msfconsole to path (or using --msf-path), it works flawlessly
Meanwhile, I'm adding these workarounds to my entrypoint.sh.
The text was updated successfully, but these errors were encountered: