-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8255867: SignatureScheme JSSE property does not preserve ordering in handshake messages #2658
Conversation
…handshake messages
👋 Welcome back jnimeh! A progress list of the required criteria for merging this PR into |
src/java.base/share/classes/sun/security/ssl/SignatureScheme.java
Outdated
Show resolved
Hide resolved
Webrevs
|
test/jdk/sun/security/ssl/SignatureScheme/SigSchemePropOrdering.java
Outdated
Show resolved
Hide resolved
src/java.base/share/classes/sun/security/ssl/SignatureScheme.java
Outdated
Show resolved
Hide resolved
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.
Looks good to me. Thanks!
@jnimeh 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 74 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. ➡️ To integrate this PR with the above commit message to the |
/integrate |
@jnimeh Since your change was applied there have been 74 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit a30fb4f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This fix adjusts the SunJSSE provider's handling of the jdk.tls.[client | server].SignatureSchemes property and its effect on messages that assert the signature_algorithms and signature_algorithms_cert extensions, or supported_signature_algorithms vectors like those used in TLS 1.2 CertificateRequest messages. With this change, the ordering of the signature algorithms in the property value will be preserved in the ordering as integer identifiers in the messages itself. Prior to this fix the property algorithms will be asserted, but in the order as shown in the sun.security.ssl.SignatureAlgorithms enumeration.
This does not affect the default ordering of these signature schemes when the property is not given a value.
JBS: https://bugs.openjdk.java.net/browse/JDK-8255867
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2658/head:pull/2658
$ git checkout pull/2658