-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Fix NSS KeyLog cannot decrypt TLS1.3 traffic. #4767
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
base: master
Are you sure you want to change the base?
Conversation
d2f40aa
to
998bdc1
Compare
Thanks for this PR. Could you add a unit test? You can have a look at the file tls.uts to check how it is done for TLS 1.2 |
Hi guedou, Thanks for the feedback. I've added the unit test.
This doesn't happen with |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4767 +/- ##
==========================================
- Coverage 81.26% 81.02% -0.24%
==========================================
Files 363 365 +2
Lines 88325 89068 +743
==========================================
+ Hits 71773 72167 +394
- Misses 16552 16901 +349
🚀 New features to boost your workflow:
|
Thanks for the update. I think that it is better to keep the TLS1.2 tests in /test/scapy/layers/tls/tls.uts and add the new ones into /test/scapy/layers/tls/tls13.uts That will ensure that both are tested and working. Your fix (i.e. using sniff()) is correct, as the error is caused by a TCP segment that is not re-fragmented: the integrity cannot be checked as the complete TLS Record is not processed. |
@hyunel can you fix the linting errors? |
Checklist:
cd test && ./run_tests
ortox
)fixes #3374