2. (10 points) Consider the trace https://www.cloudshark.org/captures/2f4535ecfabd that captures an HTTPS session and answer the questions below The trace captures encrypted traffic, so normally you would not be able to see the application layer payload. As the trace was taken, the browser (Chrome) was instructed (by starting it with-ssl-key-log-files slkeylog file.txt option) to save the SSL/TSL key for the session. The key was then uploaded to CloudShark to enable decryption. If you are curious, the same trace without an encryption key looks like https://www.cloudshark.org/captures/b45f665444e2 a. What version of HTTP is used during the session? b. What request does the HTTP client make? c. What is the server response? d. Is there a followup HTTP request? If yes, what is it for? e. How may round trips does it take to establish a TSL session, i.e., to get to the point when the client can start with HTTP? Pay attention to what is a trigger for what, this is a bit more complicated than counting packet pairs till you get to the one that contains the first HTTP command f. What is the street address in the certificate presented by the server? g. Does Chrome divulge any server secrets by allowing the session keys to be saved? h. Extra credit (5 points): After the secure connection established, the client starts communicating using HTTP/2.0. How does it know that the server is capable of handling HTTP/2.0