From 9fa1c261aa32b211be83ad700c30986f163dcbe4 Mon Sep 17 00:00:00 2001 From: John-Mark Gurney Date: Sun, 18 Apr 2021 19:32:00 -0700 Subject: [PATCH] minor fix up.. --- content/2018/10/tls-client-authentication-leaks-user.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/2018/10/tls-client-authentication-leaks-user.html b/content/2018/10/tls-client-authentication-leaks-user.html index cd753ee..4305d2a 100644 --- a/content/2018/10/tls-client-authentication-leaks-user.html +++ b/content/2018/10/tls-client-authentication-leaks-user.html @@ -32,7 +32,7 @@ profile their usage. I was confident that this was the case as I know that the entire handshake is in the clear. It isn't till the Finished messages that the session becomes encrypted. (TLS 1.3 fixed this by using a new -derived key, [sender]_handshake_traffic_secret, to encrypt all the +derived key, `[sender]_handshake_traffic_secret`, to encrypt all the server params, which the client will use to encrypt it's response to the certificate request in the server params.) I decided to verify that this was the case.