What is the intent for the "-vhost-input" option? #1472
Replies: 3 comments 1 reply
-
From my understanding, the option is used to determine if the host you are scanning is using virtual hosting. I am more interested in understanding how it determines valid vhosts, so easily. But in response to your question, I don't think it's intended to take a list of vhosts as much as it's intended for you you to feed a list of hosts and use the option to determine which hosts are vhosts and which are not. So far, in my experience it has been fairly accurate. I hope that makes sense. |
Beta Was this translation helpful? Give feedback.
-
It seems that the |
Beta Was this translation helpful? Give feedback.
-
I tried this feature and it doesn't work for me. |
Beta Was this translation helpful? Give feedback.
-
Does anyone know what the original idea for the -vhost-input httpx option was and/or is?
I'm working an httpx feature to add vhost support (setting the "Host: CustomHost>" header in the request). The help menu for -vhost-input sounds to me like it should take a list of vhosts as an input and run those as vhosts against all the targets. Is this the intended functionality?
It's currently a scanoption as a boolean value and doesn't seem like it's used much in the current release.
Looking for any feedback anyone can provide. If it turns out I have the right idea of what it's for I'll use it in my fork. If not I'll need to create a new option.
Thanks for your help!
Beta Was this translation helpful? Give feedback.
All reactions