srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index b1237f6..16a1880 100644
--- a/README.md
+++ b/README.md
@@ -204,7 +204,9 @@ another *intercepting* proxy needs that proxy's own CA trusted too -
it terminates and re-signs the connection with its own CA, which
mitmux's outbound TLS client has no reason to trust otherwise; you'll
see a clear certificate-verification error in history rather than a
-silent failure. SOCKS5 upstreams aren't implemented.
+silent failure. `-upstream-proxy socks5://[user:pass@]host:port`
+chains through a SOCKS5 proxy instead - Tor, `ssh -D`, or any other
+SOCKS5 relay - with optional username/password auth.
## Usage
@@ -557,8 +559,6 @@ reasoning behind each:
- `mitmuxd -install-ca` prints per-OS trust-store install steps; it
never runs them for you (see Quick start above for why)
- No WebSocket interception
-- Upstream proxy chaining (`-upstream-proxy`) is HTTP CONNECT only, no
- SOCKS5
- No active or passive vulnerability scanning, no plugin system - this
is a manual-testing tool, not a scanner