-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to parse TLS 1.3 Server Hello #1668
Comments
Thanks for this report! Yep, a capture file would help. |
Here's a capture. The server hello is in packet 6: |
I think the problem are the TLS1.3 version numbers. I think the message is parsed as TLSServerHello instead of TLS13ServerHello because the version number that is mentioned in the packet is 0x0303 for both TLS1.2 and TLS1.3. In handshake.py
|
Here is the new output (see my code to reproduce in the OP). This is better, but still not great.
|
Are you using the code from PR #2146 ? Here is the (truncated) output that I have when the PR is used:
|
Evidently I had the wrong branch checked out; my output now matches yours. The part after you trim is a bit odd still? |
Everything looks good on my side.
|
Closed as #2146 is merged. |
I found that I wasn't able to parse a Server Hello from the TLS 1.3 testing site https://enabled.tls13.com/ with the current development version of scapy (87916fd , Python 3, Linux).
Here's a snippet that reproduces the issue:
Code to reproduce
Wireshark knows that the first part of this is a Server Hello Handshake:
Unfortunately, Scapy doesn't:
It's getting the
version
andlen
, but not recognizing anything past that.I can provide other captures if it helps?
The text was updated successfully, but these errors were encountered: