301B practice question 25 of 30

Given this as the first packet displayed of an ssldump: 2 2 1296947622.6313 (0.0001) S>CV3.1(74) Handshake ServerHello Version 3.1 random[32]= 19 21…

Full set: 210 questions
Given this as the first packet displayed of an ssldump: 2 2 1296947622.6313 (0.0001) S>CV3.1(74) Handshake ServerHello Version 3.1 random[32]= 19 21 d7 55 c1 14 65 63 54 23 62 b7 c4 30 a2 f0 b8 c4 20 06 86 ed 9c 1f 9e 46 0f 42 79 45 8a 29 session_id[32]= c4 44 ea 86 e2 ba f5 40 4b 44 b4 c2 3a d8 b4 ad 4c dc 13 0d 6c 48 f2 70 19 c3 05 f4 06 e5 ab a9 cipherSuite TLS_RSA_WITH_RC4_128_SHA compressionMethod NULL In reviewing the rest of the ssldump, the application data is NOT being decrypted. Why is ssldump failing to decrypt the application data?
Answer options
A: The application data is encrypted with SSLv3.
B: The application data is encrypted with TLSv1.
C: The data is contained within a resumed TLS session. Correct answer
D: The BigDB Key Log.Tcpdump.Level needs to be adjusted.
Correct Answer:
C. The data is contained within a resumed TLS session.
Explanation

The ssldump output shows a ServerHello message containing a 32-byte session ID, which indicates the server is agreeing to resume a previous TLS session. For ssldump to decrypt application data, it must observe the full TLS handshake where the master secret is established. In a resumed session, the key exchange is skipped, and the master secret from the original session is reused. Since ssldump did not capture the original handshake, it lacks the necessary keying material to decrypt the traffic.

Why Incorrect

A. The ssldump output explicitly states Version 3.1, which corresponds to TLS 1.0, not SSLv3 (Version 3.0).
B. While the traffic is TLSv1, this fact alone does not explain the failure to decrypt. ssldump is fully capable of decrypting TLSv1 traffic given a full handshake.
D. This BigDB key is for logging session keys, primarily for ciphers using Perfect Forward Secrecy (PFS). The cipher used here is RSA-based, not PFS.

References

1. F5 Support. (2020). K12783074: Decrypting SSL/TLS traffic using the ssldump utility. AskF5. "If the SSL session is resumed, the ssldump utility cannot decrypt the traffic because the master secret from the initial SSL handshake is not available in the capture."

2. F5 Support. (2017). K10209: BIG-IP session resumption behavior. AskF5. This document explains how session resumption works on BIG-IP, which involves reusing a previously negotiated master secret.

Scroll to Top