Specify multiple http urls to probe - #781
Open
Frky wants to merge 2 commits into
Open
Conversation
p-l-
approved these changes
Jun 7, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR aims to bring the possibility to hit multiple HTTP endpoints with --banners for open ports. The multiple endpoints can be specified in command-line with the option
--http-url "/endpoint1,/endpoint2,/endpoint3".It uses the linked-list of banners introduced to try multiple protocols on one port.
In addition, it add an option (
--output-probes) to output in some formats the probe used to get a banner. This allows to keep info about what banner corresponds to what probe.For example:
In the output XML, we will have two different lines:
In this example, the HTTP
GETrequest to/index.htmlgives aHTTP 200 OKwhile/index.phpgives aHTTP 404 File not found.Note that without
--output-probes, masscan output is not modified, which ensures compatibility with current parsing tools.Disclaimers:
Finally, note that @p-l- already drafted the support of this new output format in Ivre (see ivre/ivre#1574).