-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8346285: Update jarsigner compatibility test for change in default digest algorithm #22765
Conversation
👋 Welcome back mdonovan! A progress list of the required criteria for merging this PR into |
@mpdonova 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 20 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 |
Webrevs
|
@@ -1439,7 +1439,9 @@ private SignItem tsaDigestAlgorithm(String tsaDigestAlgorithm) { | |||
} | |||
|
|||
String expectedTsaDigestAlg() { | |||
return tsaDigestAlgorithm != null ? tsaDigestAlgorithm : "SHA-256"; |
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.
You can actually get it from jdk.security.jarsigner.JarSigner.Builder.getDefaultDigestAlgorithm()
.
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.
I updated the code to use getDefaultDigestAlgorithm
but I still need the version-check because this test invokes jarsigner in different JDKs that use different default algorithms.
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.
LGTM. Thanks.
/integrate |
Going to push as commit e7d21fc.
Your commit was automatically rebased without conflicts. |
In this small PR, I updated the jarsigner compatibility test to handle the difference in default digest algorithms between JDK versions. The previous default was SHA-256 but has been updated to SHA-384.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22765/head:pull/22765
$ git checkout pull/22765
Update a local copy of the PR:
$ git checkout pull/22765
$ git pull https://git.openjdk.org/jdk.git pull/22765/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22765
View PR using the GUI difftool:
$ git pr show -t 22765
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22765.diff
Using Webrev
Link to Webrev Comment