JDK-8283665 : Two Jarsigner tests needs to be updated with JDK-8267319
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 19
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2022-03-25
  • Updated: 2023-01-02
  • Resolved: 2022-03-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 19
19 b16Fixed
Related Reports
Relates :  
JDK-8267319 - Use Larger Default Key Sizes and Algorithms Based on CNSA
Relates :  
JDK-8277474 - jarsigner does not check if algorithm parameters are disabled
Relates :  
JDK-8282633 - jarsigner output does not explain why an EC key is disabled if its curve has been disabled
Description
Two jarsigner tests, i.e. test/jdk/sun/security/tools/jarsigner/DisableCurveTest.java and test/jdk/sun/security/tools/jarsigner/CheckAlgParams.java, failed after JDK-8267319 is merged in. These tests are added to the main trunk during the peer review of JDK-8267319. Thus, running mach5 on the forked off branch did not catch this. 
These tests are written with the pre-JDK-8267319 behavior and needs to be updated.
Comments
The fix for this bug is integrated in jdk-19+16-990.
25-03-2022
Changeset: 3b5dfee9 Author: Valerie Peng <valeriep@openjdk.org> Date: 2022-03-25 17:10:59 +0000 URL: https://git.openjdk.java.net/jdk/commit/3b5dfee939dda02e14498baa2b52b0150326b938
25-03-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/7952 Date: 2022-03-25 05:11:18 +0000
25-03-2022
JDK-8277474 and JDK-8282633 are integrated while JDK-8267319 is being forked off and reviewed. In order to prevent this from happening again, the branch of JDK-8267319 would need to sync with master and re-test again before integration.
25-03-2022