summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorEvgeny Zinoviev <me@ch1p.io>2021-02-16 02:06:20 +0300
committerEvgeny Zinoviev <me@ch1p.io>2021-02-16 02:06:20 +0300
commitf265dc59b3fbcbdc520d34d2a756c2cf472c06a0 (patch)
tree6939627d5800dcb700a7996a635140c8cf853caf /README.md
parentd9ea8224613d5bd27bf527b14fa4ef02f827e482 (diff)
update readmeHEADmaster
Diffstat (limited to 'README.md')
-rw-r--r--README.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/README.md b/README.md
index 4fb1867..3fa6b41 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,12 @@
-This script is ad-hoc solution for inspecting **MQTT over TLS** traffic. As far as I know Wireshark solves this problem but obtaining TLS master keys from IoT device might be a pain. Also you can log MQTT topics, just uncomment lines at the bottom of the `plugin.py`.
+This script is ad-hoc solution for inspecting **MQTT over TLS** traffic.
+
+This is a continuation of work started in [mitmproxy-mqtt-script](https://github.com/nikitastupin/mitmproxy-mqtt-script).
+This fork supports (almost) all MQTT packet types, multiple packets handling, and more.
## Usage
-Run mitmproxy as `mitmproxy --mode transparent --tcp-hosts '.*' -s mqtt_message.py`. Messages will be displayed at the event log (press `shift + e`).
+Run mitmproxy as `mitmproxy --mode transparent --tcp-hosts '.*' -s plugin.py`. Messages will be displayed at the event
+log (press `shift + e`).
Of course before that you have to prepare a target device and your host running mitmproxy:
* Install mitmproxy's root certificate on a target device.