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

ntlmrelayx.py: Make SOCKS5 address and port configurable #1636

Merged
merged 2 commits into from
Jan 11, 2024

Conversation

rtpt-erikgeiser
Copy link
Contributor

@rtpt-erikgeiser rtpt-erikgeiser commented Oct 24, 2023

This PR adds the option -socks-address and -socks-port which makes the SOCKS5 server address and port configurable. By setting the default address to 127.0.0.1 it also fixes #1532 which can actually be seen as a huge security issue as sensitive connections are exposed on all interfaces. Having the option to change the port is also useful for multi-user setups.

The address part of -socks-address is also used for the SOCKS HTTP API on port 9090 (configurable with -http-api-port). Of course this also means that the web API now also uses 127.0.0.1 by default which is also a security improvement in my opinion.

@anadrianmanrique anadrianmanrique added the medium Medium priority item label Oct 26, 2023
@rtpt-erikgeiser rtpt-erikgeiser force-pushed the configurable_socks_address branch 2 times, most recently from 655e964 to 72df5fb Compare November 9, 2023 10:31
@rtpt-erikgeiser rtpt-erikgeiser force-pushed the configurable_socks_address branch from 72df5fb to b183343 Compare November 9, 2023 10:49
@enj5oy
Copy link

enj5oy commented Nov 24, 2023

@gabrielg5 can you please merge this pull request?

@gabrielg5 gabrielg5 merged commit 6c9a1aa into fortra:master Jan 11, 2024
9 checks passed
@gabrielg5
Copy link
Collaborator

To master! 🚀

thanks for the nice addition @rtpt-erikgeiser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium Medium priority item
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SOCKS server listens on all interfaces by default
4 participants