Accept underscore as valid char in hostname strings #430
Conversation
This file contains 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.
What:
Accept underscore as valid char in hostname strings
Why:
Underscore is allowed for domain names, but not for hostnames. Despite it is not recommended at all, it can be desirable to use it. Under the premise "the scanner must do the best it can" it is now allowed.
RFC for hostnames: https://tools.ietf.org/html/rfc819
RFC for domain name syntax https://tools.ietf.org/html/rfc2181
How:
Scan a target which includes a host with an underscore in the name
Checklist: