UPSTREAM PR #30924: TLS 1.3 Ticket Renewal on Cipher Change#679
Open
loci-dev wants to merge 1 commit into
Open
UPSTREAM PR #30924: TLS 1.3 Ticket Renewal on Cipher Change#679loci-dev wants to merge 1 commit into
loci-dev wants to merge 1 commit into
Conversation
For TLS 1.3 session resumption, when the client's identity (a.k.a "ticket") is for a cipher which is not the same one we want to negotiate, we should issue a new ticket with an updated identity and the cipher we want to negotiate
loci-dev
had a problem deploying
to
PROD__AL_DEMO
GitHub Actions
Failure
loci-dev
force-pushed
the
main
branch
5 times, most recently
from
421b135 to
770bf14
Compare
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.
Note
Source pull request: openssl/openssl#30924
For TLS 1.3 session resumption, when the client's identity (a.k.a "ticket") is for a cipher which is not the same one we want to negotiate, we should issue a new ticket with an updated identity and the cipher we want to negotiate