changes to disable LDAP and FTP in responder when they are used by "interactsh" #987
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.
Now if someone wants to use interact + responder (docker) it will fail and the responder docker does not start. This is because by default interactsh starts a LDAP server on port 389, and the default command for responder docker uses this port too.
The "docker run" command fails and does not start.
There should be an option for disabling "interact"LDAP server completly so there is not ports conflicts with the "responder" command.
This change takes cares of this option, and changes the "docker run" command so there is no port conflicts with LDAP or FTP.