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
8266225: jarsigner is using incorrect security property to show weakness of certs #3905
Conversation
|
@haimaychao The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
/label remove core-libs compiler |
@wangweij The |
@@ -88,5 +88,32 @@ public static void main(String[] args) throws Exception { | |||
// key, but not for its SHA1withRSA algorithm. | |||
.shouldContain("Signature algorithm: SHA1withRSA, 1024-bit key (weak)") | |||
.shouldHaveExitValue(0); |
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.
What does the test show before this fix?
I don't see Security.setProperty
called or a new java.security
file is used. If jdk.jar.dA
and jdk.certpath.dA
are the same, then there's no way to find out if the new code works.
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.
Added test using new java.security with different disabledAlgorithms for certpath and jar.
@haimaychao This change now passes all automated pre-integration checks. 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 79 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.
|
@wangweij @seanjmullan Thanks for the review. |
/integrate |
@haimaychao Since your change was applied there have been 79 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 995e956. |
Please review the change to jarsigner so it uses certpath security property in order to properly display the weakness of the certificate algorithms.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3905/head:pull/3905
$ git checkout pull/3905
Update a local copy of the PR:
$ git checkout pull/3905
$ git pull https://git.openjdk.java.net/jdk pull/3905/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3905
View PR using the GUI difftool:
$ git pr show -t 3905
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3905.diff