summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Burwell <ben@benburwell.com>2021-05-14 15:26:35 -0400
committerBen Burwell <ben@benburwell.com>2021-05-14 15:26:35 -0400
commitb503b33f4cf07041a8e1e5c44c5cf1ddbb195ea1 (patch)
tree5d634b6be2077181ac6ed7e0b5bfa0a9b4c10e58
parentc845403fd4be2b719364f98ee4be9e82a39639e1 (diff)
fixup! Add TLS Wireshark postHEADmaster
-rw-r--r--_posts/2021-05-14-intercepting-golang-tls-with-wireshark.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/_posts/2021-05-14-intercepting-golang-tls-with-wireshark.md b/_posts/2021-05-14-intercepting-golang-tls-with-wireshark.md
index ee86fe9..4b51c15 100644
--- a/_posts/2021-05-14-intercepting-golang-tls-with-wireshark.md
+++ b/_posts/2021-05-14-intercepting-golang-tls-with-wireshark.md
@@ -7,13 +7,13 @@ services][mitmproxy-post]. This is a continued exploration of debugging network
services, in particular focused around inspecting TLS encrypted traffic that
your application is sending and receiving.
-Transport Layer Security is a fundamental building block of secure
-communications on the Internet today, and increasingly the software we write is
+Transport Layer Security is a fundamental building block of modern secure
+communications on the Internet, and increasingly the software we write is
expected to be a fluent speaker of TLS. While this brings security benefits for
users, it also increases the complexity of understanding what our software is
doing because when we try to use tools like Wireshark or tcpdump to inspect
network traffic, all we see is encrypted data. Let's see what a regular HTTP
-request looks like in Wireshark:
+request looks like in Wireshark:
```
$ curl http://www.benburwell.com
@@ -22,8 +22,8 @@ $ curl http://www.benburwell.com
![A Wireshark packet capture showing a plain HTTP request and
response](https://s.bnbl.io/blog/tls-wireshark/plain.png)
-Here, we can see the HTTP request and response. But what happens when we make
-the request over TLS?
+Here, we can see the HTTP request and response. But what happens when we make
+the request over TLS?
```
$ curl https://www.benburwell.com