8278349: JarSigner javadoc example uses SHA-1

[eirbjo]

Please review this trivial PR which updates javadoc sample code in jdk.security.jarsigner.JarSigner to use SHA-256, SHA256withRSA instead of the now considered weak algorithms SHA-1, SHA1withDSA.

The sample code is also updated to use the new snippet syntax.

---

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-8278349: JarSigner javadoc example uses SHA-1

Reviewers

• Weijun Wang (@wangweij - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 11992

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

Using diff file

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

[bridgekeeper]

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

@eirbjo 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.

[mlbridge]

Webrevs

• 01: Full - Incremental (56079e31)
• 00: Full (b288d1fd)

[openjdk]

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

8278349: JarSigner javadoc example uses SHA-1

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 1 new commit pushed to the master branch:

• d117979: 8300054: Use static_assert in basic_types_init

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.

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).

[wangweij]

@eirbjo, you can now type /integrate and I'll type /sponsor. Thanks for the fix!

[eirbjo]

/integrate

[wangweij]

/sponsor

[openjdk]

@eirbjo
Your change (at version 56079e3) is now ready to be sponsored by a Committer.

[openjdk]

Going to push as commit 4ec3659.
Since your change was applied there has been 1 commit pushed to the master branch:

• d117979: 8300054: Use static_assert in basic_types_init

Your commit was automatically rebased without conflicts.

[openjdk]

@wangweij @eirbjo Pushed as commit 4ec3659.

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