8278851: Correct signer logic for jars signed with multiple digestalgs

[GoeLin]

I backport this for parity with 17.0.4-oracle.

JarVerifier: resolve due to context.
ManifestEntryVerifier.java: I had to remove an argument 'false' because "JDK-8275887: jarsigner prints invalid digest/signature algorithm warnings if keysize is weak/disabled" is not in 17.

I had to add a hunk from "JDK-8269039: Disable SHA-1 Signed JARs" to
SecurityUtils.java to make a method public that is called in a test.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8278851: Correct signer logic for jars signed with multiple digestalgs

Reviewers

• Matthias Baesken (@MBaesken - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/262/head:pull/262
$ git checkout pull/262

Update a local copy of the PR:
$ git checkout pull/262
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/262/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 262

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/262.diff

[bridgekeeper]

👋 Welcome back goetz! 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]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (9d82caee)

[MBaesken]

LGTM

[openjdk]

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

8278851: Correct signer logic for jars signed with multiple digestalgs

Reviewed-by: mbaesken

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

• 32148d2: 8276796: gc/TestSystemGC.java large pages subtest fails with ZGC
• fbe05ec: 8280476: [macOS] : hotspot arm64 bug exposed by latest clang

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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 master branch, type /integrate in a new comment.

[GoeLin]

/integrate

[openjdk]

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

• 32148d2: 8276796: gc/TestSystemGC.java large pages subtest fails with ZGC
• fbe05ec: 8280476: [macOS] : hotspot arm64 bug exposed by latest clang

Your commit was automatically rebased without conflicts.

[openjdk]

@GoeLin Pushed as commit cbe4973.

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