Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow dirsearch to use a non-default network interface #1323 #1325

Merged
merged 4 commits into from
Sep 19, 2023
Merged

Allow dirsearch to use a non-default network interface #1323 #1325

merged 4 commits into from
Sep 19, 2023

Conversation

huyphan
Copy link
Contributor

@huyphan huyphan commented Sep 19, 2023

Description

This change allows users to configure dirsearch to use specific network interface instead of the default one. This is useful for those who have more than one egress interfaces on their machines.

Testing

With the change in place, I was able to pick the network interface when running dirsearch (targetting my own service) and could verify that dirsearch did pick up the designated interface (by looking at the access log of my server).

$ tcpdump --list-interfaces
1.eno1 [Up, Running, Connected]
2.wg0 [Up, Running]

# These two commands resulted in two different IPs being logged in my service's access logs. 
$ pipenv run python dirsearch.py -u <my-service> --interface eno1
$ pipenv run python dirsearch.py -u <my-service> --interface wg0

Requirements

  • Add your name to CONTRIBUTERS.md
  • If this is a new feature, then please add some additional information about it to CHANGELOG.md

@huyphan huyphan marked this pull request as ready for review September 19, 2023 13:35
@shelld3v shelld3v merged commit 759d089 into maurosoria:master Sep 19, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants