-
Notifications
You must be signed in to change notification settings - Fork 271
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
Unknown or invalid cipher suite type X #587
Comments
Relevant piece of the ja3 code here: https://github.com/salesforce/ja3/blob/master/python/ja3.py#L177 |
Looks like dpkt's SSL decoder fails to recognize one of the reserved GREASE cipher suite values ( This code block raises an exception if the given cipher suite is not known (i.e. not defined in ssl_ciphersuites.py) I think dpkt should have more permissive logic - i.e. it should not abort parsing the TLS record when it encounters an unknown (to dpkt) cipher suite. I will submit a fix for this |
Thanks for this quick reaction! Looking forward to the fix! |
PR #588 is up |
@HugooB I've now merged the fix into master. Please see if it helps resolve the issue (you'll need to install dpkt from master). |
Improvements to TLS ClientHello and ServerHello parsing: * return an "Unknown" CipheSsuite instead of raising an exception; * add codes for RFC8701, GREASE ciphersutes; * CipherSuite __repr__ now includes the numerical code; * rename some attributes to align between ClientHello and ServerHello classes, original names still supported.
1.9.4 doesn't produce this error, 1.9.5 and 1.9.6 both do. related: salesforce/ja3#59 |
@LouAlbano this was fixed in 1.9.7 (latest release). I will double check and comment on the ja3 issue |
Describe the bug
Parsing HTTPS packets results in the following error:
dpkt.ssl.SSL3Exception: Unknown or invalid cipher suite type X
. There is a similar issue on the Salesforce JA3 git: salesforce/ja3#59 . Downgrading to 1.9.2 solves the issue.To Reproduce
dpkt
latest version (1.9.6)Expected behavior
It should work
Details(please complete the following information):
Additional context
salesforce/ja3#59
The text was updated successfully, but these errors were encountered: