Assignment 15 1: HTTP(s) TLS - savannahc502/SavC-TechJournal-NET215 GitHub Wiki

<form action="welcome_get.php" method="get">
      First Name: <input type="text" name=“first_name"><br>
     Last Name: <input type="text" name=“last_name"><br>
      <input type="submit">
  </form>
  • parameter1 = first_name
  • parameter2 = last_name

Other Notes:

  • POST METHODS always have the request in the body.
  • A GET request will NOT have a body
  • Make sure to differentiate the HTTP/HTTPS request from the response
    • Both POST and GET responses will have a body of the request information (or an error)
  • TLS operates at the presentation layer of the OSI stack
  • TCP is the transport layer protocol used by TLS
  • HTTPS used TLS to establish secure communications
  • In an https session, after the 3-way handshake, the first few packets are in plaintext as the symmetric key has not been exchanged yet

My Description of TLS Handshake and Authentication Process:

In a TLS handshake and authentication process, the client and server must first establish a connection using the typically SYN, SYN-ACK, ACK 3-way handshake. Once the initial connection is established, the client will send a "Client Hello" that contains the requested TLS version, session ID for the rest of the TLS process, and a random number (for the symmetric key later). The Server will send a "Server Hello" back to acknowledge the receipt of the client hello, confirm the TLS version, and send a second random number. The server will immediately follow up with a digital certificate containing its public key for the asymmetric encryption, and a Server Hello Done message when complete.

Know, the client has to send a pre-master secret key to the server. This key is encrypted with the server's public key, so only the server can read it. The master key for the rest of the session is generated using this pre-master key and the two random numbers from earlier. This process uses asymmetric encryption to securely create a symmetric key for the client and server to share. The Client and Server send each other a Handshake Finished message once they both have this new master key, and they are ready to encrypt plaintext messages.

⚠️ **GitHub.com Fallback** ⚠️