SOCKS5 listener #8

New issue

Closed

opened 2026-10-26 20:23:18 +00:00 by mikluko · 0 comments

mikluko commented

2026-10-26 20:23:18 +00:00

Owner

Some environments hand a client both an HTTP and a SOCKS proxy, and tools that only speak SOCKS (nc -X 5, some database drivers) use the latter. A SOCKS5 listener routed by the same hostname rules (tunnel, MITM, refuse) would cover them, and stop a SOCKS path from sidestepping the HTTP proxy's rules.

Some environments hand a client both an HTTP and a SOCKS proxy, and tools that only speak SOCKS (`nc -X 5`, some database drivers) use the latter. A SOCKS5 listener routed by the same hostname rules (tunnel, MITM, refuse) would cover them, and stop a SOCKS path from sidestepping the HTTP proxy's rules.

mikluko added the

enhancement

label

2026-10-26 20:23:18 +00:00

mikluko referenced this issue from a commit

2026-10-26 21:06:06 +00:00

SOCKS5 listener

mikluko referenced this issue from a pull request that will close it,

2026-10-26 21:06:14 +00:00

SOCKS5 listener #33

mikluko closed this issue

2026-10-26 21:07:02 +00:00