8277474: jarsigner does not check if algorithm parameters are disabled

[haimaychao]

This fixes jarsigner to enforce checking against algorithm constraint properties so when the signature algorithms parameters use disabled or legacy algorithms, it will emit warnings accordingly. If the algorithm used in parameters is disabled, jarsigner treats the jar as unsigned.

---

Progress

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

Issue

• JDK-8277474: jarsigner does not check if algorithm parameters are disabled

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7580/head:pull/7580
$ git checkout pull/7580

Update a local copy of the PR:
$ git checkout pull/7580
$ git pull https://git.openjdk.java.net/jdk pull/7580/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 7580

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7580.diff

[bridgekeeper]

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

@haimaychao The following labels will be automatically applied to this pull request:

• compiler
• core-libs
• security

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.

[mlbridge]

Webrevs

• 00: Full (1d2c4c17)

[haimaychao]

/label remove core-libs

[haimaychao]

/label remove compiler

[openjdk]

@haimaychao
The core-libs label was successfully removed.

[openjdk]

@haimaychao
The compiler label was successfully removed.

[haimaychao]

/open