From ef13270ff2663ccfc5b99af5120e9c8cadc513a0 Mon Sep 17 00:00:00 2001 From: sidahmed-malaoui Date: Fri, 10 Jul 2020 12:43:37 +0100 Subject: [PATCH] Command that can generates errors in the documentation In the title _Work-around to redirect traffic originating from the machine itself_, add the flag `-H` to `sudo` command to avoid errors on certain Linux based OS. --- docs/src/content/howto-transparent.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/content/howto-transparent.md b/docs/src/content/howto-transparent.md index 2943aae42..006f40835 100644 --- a/docs/src/content/howto-transparent.md +++ b/docs/src/content/howto-transparent.md @@ -94,7 +94,7 @@ Create a user to run the mitmproxy ```bash sudo useradd --create-home mitmproxyuser -sudo -u mitmproxyuser bash -c 'cd ~ && pip install --user mitmproxy' +sudo -u mitmproxyuser -H bash -c 'cd ~ && pip install --user mitmproxy' ``` Then, configure the iptables rules to redirect all traffic from our local machine to mitmproxy. **Note**, as soon as you run these, you won't be able to perform successful network calls *until* you start mitmproxy. If you run into issues, `iptables -t nat -F` is a heavy handed way to flush (clear) *all* the rules from the iptables `nat` table (which includes any other rules you had configured). @@ -108,7 +108,7 @@ ip6tables -t nat -A OUTPUT -p tcp -m owner ! --uid-owner mitmproxyuser --dport 4 This will redirect the packets from all users other than `mitmproxyuser` on the machine to mitmproxy. To avoid circularity, run mitmproxy as the user `mitmproxyuser`. Hence step **4** should look like: ```bash -sudo -u mitmproxyuser bash -c '$HOME/.local/bin/mitmproxy --mode transparent --showhost --set block_global=false' +sudo -u mitmproxyuser -H bash -c '$HOME/.local/bin/mitmproxy --mode transparent --showhost --set block_global=false' ```