Allow user-specified EHLO domains in SMTP STARTTLS #1258
Closed
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
if no EHLO hostname is supplied, then fall-back to the default in smtp.lua
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.
The web documentation for ssl-enum-ciphers implies that a user can specify an EHLO hostname on the command line as a script argument:
But currently, "EHLO example.com" is sent regardless of
smtp.domainbeing specified.The hardcoded
"example.com"is replaced bysmtp.get_domain()allowing the EHLO hostname to be specified as an arg, or to fall back to the default insmtp.lua(currenly"nmap.scanme.org")