From c845403fd4be2b719364f98ee4be9e82a39639e1 Mon Sep 17 00:00:00 2001 From: Ben Burwell Date: Fri, 14 May 2021 15:16:45 -0400 Subject: Add link from mitmproxy post to wireshark post --- _posts/2021-05-06-debugging-http-services-with-mitmproxy.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to '_posts') diff --git a/_posts/2021-05-06-debugging-http-services-with-mitmproxy.md b/_posts/2021-05-06-debugging-http-services-with-mitmproxy.md index 8c5d7c9..c4e26f8 100644 --- a/_posts/2021-05-06-debugging-http-services-with-mitmproxy.md +++ b/_posts/2021-05-06-debugging-http-services-with-mitmproxy.md @@ -83,8 +83,10 @@ using a TLS key log file, but this usually involves making somewhat non-trivial modifications to the program you're working with. It's not _very_ complicated or difficult, and it's a technique I've used a few times, but mitmproxy is usually quicker and easier for me. I plan to write a post about this topic in the -future, so stay tuned! +future, so stay tuned! _(Update: see [my post about decrypting TLS in +Wireshark][wireshark-tls])_ [mitmproxy]: https://mitmproxy.org/ [honey badger]: https://youtu.be/4r7wHMg5Yjg [certs]: https://docs.mitmproxy.org/stable/concepts-certificates/ +[wireshark-tls]: ../intercepting-golang-tls-with-wireshark/ -- cgit v1.2.3