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

Fixed bug that caused nc to bind to random port #14

Merged
merged 4 commits into from
Sep 4, 2020

Conversation

CrossedWires
Copy link
Contributor

I just updated the nc calls to make them bind to the correct port. Nothing major.

@CrossedWires
Copy link
Contributor Author

I also modified the command line arguments to work with IP address instead of interface for several reason:

  1. rsg converts interface to ip address anyway so it's silly to name the interface name
  2. when generating reverse shells with the "all" interface name setting, the generated reverse shells are set to connect back to 0.0.0.0 instead of the address of the attacking machine
  3. More explicit listener on set IP address removes confusion when reverse shell fails to bind

@mthbernardes mthbernardes merged commit dfa68c4 into mthbernardes:master Sep 4, 2020
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