Skip to content
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

8345134: Test sun/security/tools/jarsigner/ConciseJarsigner.java failed: unable to find valid certification path to requested target #23001

Closed
wants to merge 4 commits into from

Conversation

myankelev
Copy link
Member

@myankelev myankelev commented Jan 9, 2025

Changed the gencert, so the certificate is now initialised to be with a start time of -1M. This prevents a potential error with the certificate not yet being valid.
Similar solution to this pull request
Have tested the test 6000 times for stability and all have passed.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8345134: Test sun/security/tools/jarsigner/ConciseJarsigner.java failed: unable to find valid certification path to requested target (Bug - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23001/head:pull/23001
$ git checkout pull/23001

Update a local copy of the PR:
$ git checkout pull/23001
$ git pull https://git.openjdk.org/jdk.git pull/23001/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23001

View PR using the GUI difftool:
$ git pr show -t 23001

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23001.diff

Using Webrev

Link to Webrev Comment

…failed: unable to find valid certification path to requested target

set the date as -1M in the cert to prevent the future cert from being used.
@bridgekeeper
Copy link

bridgekeeper bot commented Jan 9, 2025

👋 Welcome back myankelev! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jan 9, 2025

@myankelev 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:

8345134: Test sun/security/tools/jarsigner/ConciseJarsigner.java failed: unable to find valid certification path to requested target

Reviewed-by: weijun

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 162 new commits pushed to the master branch:

  • 63cedaf: 8347334: JimageDiffGenerator code clean-ups
  • 254e840: 8340416: Remove ArchiveBuilder::estimate_archive_size()
  • 8193ba3: 8347562: javac crash due to type vars in permits clause
  • 7df21a8: 8347597: HttpClient: improve exception reporting when closing connection
  • b0e2be6: 8347729: Replace SIZE_FORMAT in parallel and serial gc
  • d4e5ec2: 8346610: Make all imports consistent in the FFM API
  • c36200b: 8347721: Replace SIZE_FORMAT in compiler directories
  • af3f5d8: 8347039: ThreadPerTaskExecutor terminates if cancelled tasks still running
  • 91197b3: 8347531: The signal tests are failing after JDK-8345782 due to an unrelated warning
  • 4f3dc9d: 8347352: RISC-V: Cleanup bitwise AND assembler routines
  • ... and 152 more: https://git.openjdk.org/jdk/compare/f1196638b347c9a2e7d7dc1795c6c24ea7efe711...master

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 (@wangweij) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the rfr Pull request is ready for review label Jan 9, 2025
@openjdk
Copy link

openjdk bot commented Jan 9, 2025

@myankelev The following label will be automatically applied to this pull request:

  • security

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.

@openjdk openjdk bot added the security security-dev@openjdk.org label Jan 9, 2025
@mlbridge
Copy link

mlbridge bot commented Jan 9, 2025

Webrevs

@openjdk
Copy link

openjdk bot commented Jan 9, 2025

@myankelev Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@wangweij
Copy link
Contributor

There are many certificates created in this test. Why are only these 2 lines updated?

@myankelev
Copy link
Member Author

There are many certificates created in this test. Why are only these 2 lines updated?

changed to apply to all certificates if -startdate not specified in the command

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jan 15, 2025
@myankelev
Copy link
Member Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jan 15, 2025
@openjdk
Copy link

openjdk bot commented Jan 15, 2025

@myankelev
Your change (at version bcc232d) is now ready to be sponsored by a Committer.

@wangweij
Copy link
Contributor

/sponsor

@openjdk
Copy link

openjdk bot commented Jan 15, 2025

Going to push as commit a0f7982.
Since your change was applied there have been 162 commits pushed to the master branch:

  • 63cedaf: 8347334: JimageDiffGenerator code clean-ups
  • 254e840: 8340416: Remove ArchiveBuilder::estimate_archive_size()
  • 8193ba3: 8347562: javac crash due to type vars in permits clause
  • 7df21a8: 8347597: HttpClient: improve exception reporting when closing connection
  • b0e2be6: 8347729: Replace SIZE_FORMAT in parallel and serial gc
  • d4e5ec2: 8346610: Make all imports consistent in the FFM API
  • c36200b: 8347721: Replace SIZE_FORMAT in compiler directories
  • af3f5d8: 8347039: ThreadPerTaskExecutor terminates if cancelled tasks still running
  • 91197b3: 8347531: The signal tests are failing after JDK-8345782 due to an unrelated warning
  • 4f3dc9d: 8347352: RISC-V: Cleanup bitwise AND assembler routines
  • ... and 152 more: https://git.openjdk.org/jdk/compare/f1196638b347c9a2e7d7dc1795c6c24ea7efe711...master

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jan 15, 2025
@openjdk openjdk bot closed this Jan 15, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jan 15, 2025
@openjdk
Copy link

openjdk bot commented Jan 15, 2025

@wangweij @myankelev Pushed as commit a0f7982.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integrated Pull request has been integrated security security-dev@openjdk.org
Development

Successfully merging this pull request may close these issues.

3 participants