From b577dd93d3d8ab1eb8f8b4fb49cc4324c1a8c335 Mon Sep 17 00:00:00 2001 From: pancho horrillo Date: Fri, 6 Sep 2019 13:42:56 +0200 Subject: [PATCH] Fix usage of sudo to prevent issues with the environment. Also fix a couple of typos. --- poc/examples/tcpdump/README.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/poc/examples/tcpdump/README.md b/poc/examples/tcpdump/README.md index c51894a..6f40523 100644 --- a/poc/examples/tcpdump/README.md +++ b/poc/examples/tcpdump/README.md @@ -1,16 +1,15 @@ Remote tcpdump sniffer with source filtering ============================================ -1. Add any filter you want to the tcpdump command inside `tcpdump.pow` to filter +1. Add any filter you want to the `tcpdump` command inside `tcpdump.pow` to filter any traffic you don't want to be sniffed! -2. For the sake of simplicity run `sudo kapow server tcpdump.pow`. In a - production environment tcpdump should be run with the appropiate permissions - but kapow can (and should) run as an unprivilieged user. -3. In your local machine run: - ```bash - curl http://localhost:8080/sniff/ | sudo wireshark -k -i - +2. For the sake of simplicity, run `sudo kapow server tcpdump.pow`. In a + production environment, `tcpdump` should be run with the appropiate permissions, + but kapow can (and should) run as an unprivileged user. +3. In your local machine run: ```bash + curl http://localhost:8080/sniff/ | sudo -E wireshark -k -i - ``` - Again, for the sake of simplicity Wireshark is running as root. If you don't want - to run it this way follow this guide: + Again, for the sake of simplicity, `Wireshark` is running as root. If you don't want + to run it this way, follow this guide: https://gist.github.com/MinaMikhailcom/0825906230cbbe478faf4d08abe9d11a 4. Profit!