RFR: 8282633: jarsigner output does not explain why an EC key is disabled if its curve has been disabled
Weijun Wang
weijun at openjdk.java.net
Tue Mar 15 01:20:39 UTC 2022
On Mon, 14 Mar 2022 17:41:28 GMT, Hai-May Chao <hchao at openjdk.org> wrote:
> When a named curve is disabled in `jdk.disabled.namedCurves` property which is included in `jdk.jar.disabledAlgorithms` and `jdk.certpath.disabledAlgorithms`, `jarsigner` should display the disabled named curve as a result of its disabled algorithm constraint checking. This clarifies why an EC key is disabled in its warning and verbose output.
I think `include jdk.disabled.namedCurves` can also appear in the legacy algorithms, so it's likely there should also be a "key.bit.eccurve.weak" for jarsigner.
-------------
PR: https://git.openjdk.java.net/jdk/pull/7810
More information about the security-dev
mailing list