Browse Source

minor fix up..

main
John-Mark Gurney 4 years ago
parent
commit
9fa1c261aa
1 changed files with 1 additions and 1 deletions
  1. +1
    -1
      content/2018/10/tls-client-authentication-leaks-user.html

+ 1
- 1
content/2018/10/tls-client-authentication-leaks-user.html View File

@@ -32,7 +32,7 @@ profile their usage.
I was confident that this was the case as I know that the entire 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 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 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 server params, which the client will use to encrypt it's response to
the certificate request in the server params.) I decided to verify the certificate request in the server params.) I decided to verify
that this was the case. that this was the case.


Loading…
Cancel
Save