RFC 8446 6.2 / RFC 5246 7.2.2 - no writes after fatal alert - #11365
Open
twcook86 wants to merge 1 commit into
Open
RFC 8446 6.2 / RFC 5246 7.2.2 - no writes after fatal alert#11365twcook86 wants to merge 1 commit into
twcook86 wants to merge 1 commit into
Conversation
|
twcook86
force-pushed
the
tls_rfc8446_6.2
branch
from
September 4, 2026 22:07
b10a8cf to
789ecb1
Compare
Contributor
Author
|
retest this please. missing log |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Conform to RFC 8446 6.2 / RFC 5246 7.2.2 - no writes after fatal alert
Fixes #11073
Testing
Added new test case test_tls13_no_app_data_after_fatal_alert()
Checklist