RFR: 8277474: jarsigner does not check if algorithm parameters are disabled [v5]
Hai-May Chao
hchao at openjdk.java.net
Thu Mar 3 21:12:47 UTC 2022
> 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.
Hai-May Chao has updated the pull request incrementally with one additional commit since the last revision:
Use algname in output
-------------
Changes:
- all: https://git.openjdk.java.net/jdk/pull/7582/files
- new: https://git.openjdk.java.net/jdk/pull/7582/files/2a73d1ef..d2cd7ef8
Webrevs:
- full: https://webrevs.openjdk.java.net/?repo=jdk&pr=7582&range=04
- incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=7582&range=03-04
Stats: 14 lines in 1 file changed: 0 ins; 8 del; 6 mod
Patch: https://git.openjdk.java.net/jdk/pull/7582.diff
Fetch: git fetch https://git.openjdk.java.net/jdk pull/7582/head:pull/7582
PR: https://git.openjdk.java.net/jdk/pull/7582
More information about the security-dev
mailing list