You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: We worked around this issue by refusing TLS 1.3 connections and favoring 1.2 or others instead. This was merged in #193. This ticket initially reported the bug that was worked-around but is now used to track the efforts to support TLS 1.3 itself.
The CLIENT_RANDOM isn't enough to decrypt TLSv1.3 traffic. The following zip contains a pcap with TLSv1.3, the CLIENT_RANDOM, and a TLS debug file.
This seems to be caused by the fact that the format of the CLIENT_RANDOM has changed and is not fixed-length anymore, and that CLIENT_HANDSHAKE_TRAFFIC_SECRET should be used instead.
This should be a simple change in PyRDP, but I’m unsure how it can be done.
obilodeau
changed the title
TLSv1.3 established between client and MITM isn't decryptable with only CLIENT_RANDOM
Add support for TLSv1.3 CLIENT_HANDSHAKE_TRAFFIC_SECRET
Mar 25, 2020
Update: We worked around this issue by refusing TLS 1.3 connections and favoring 1.2 or others instead. This was merged in #193. This ticket initially reported the bug that was worked-around but is now used to track the efforts to support TLS 1.3 itself.
The CLIENT_RANDOM isn't enough to decrypt TLSv1.3 traffic. The following zip contains a pcap with TLSv1.3, the CLIENT_RANDOM, and a TLS debug file.
debug.zip
The text was updated successfully, but these errors were encountered: