-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
scan localhost? #210
Labels
Comments
Local scan mode(without ssh) is not yet supported. For now, you have to run SSHd on the target host. |
kotakanbe
added a commit
that referenced
this issue
Jan 12, 2017
If the scan target server is localhost, Don't use SSH. #210
9 tasks
kotakanbe
added a commit
that referenced
this issue
Jan 12, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 12, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 12, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 12, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 12, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
kotakanbe
added a commit
that referenced
this issue
Jan 16, 2017
If the scan target server is localhost, Don't use SSH. #210
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm just trying out vuls, i installed docker on my vps and am following the instructions, but i do not understand the config.toml configuration step. I want to run this inside a docker container and want to scan the docker host with it. I do not know how to configure the config.toml file so it does not use ssh to connect to the host.
Please let me know if there is a simple setup like this, or if i am missing something here.
Thanks,
The text was updated successfully, but these errors were encountered: