-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8277881 Missing SessionID in TLS1.3 resumption in compatibility mode #6583
Conversation
👋 Welcome back djelinski! A progress list of the required criteria for merging this PR into |
@djelinski The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add " 2021," to the copyright of ResumeTLS13withSNI.java.
I have run all the tests and they pass.
Have you run this fix on your customer's setup or similar setup to confirm this fixed their problem?
Thanks @ascarpino for reviewing. Copyright year updated. Yes I confirmed that the updated version fixes the problem. Interestingly, aside from the empty SessionID there were no other differences between the initial and resumption ClientHello messages, i.e. pre_shared_key extension was absent in both. I suppose the server didn't send any NewSessionTicket, but didn't investigate it further. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
|
@djelinski This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 385 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@ascarpino) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@djelinski |
/sponsor |
Going to push as commit 9d99a37.
Your commit was automatically rebased without conflicts. |
@ascarpino @djelinski Pushed as commit 9d99a37. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
All TLS 1.3 handshakes in compatibility mode must send a non-empty SessionID field. Currently TLS1.3 session resumptions are sending empty session ID. This patch fixes that problem.
All jdk_core tests passed. The newly added check passes with the patch, fails without it.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6583/head:pull/6583
$ git checkout pull/6583
Update a local copy of the PR:
$ git checkout pull/6583
$ git pull https://git.openjdk.java.net/jdk pull/6583/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6583
View PR using the GUI difftool:
$ git pr show -t 6583
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6583.diff