JDK-8267100 : [BACKOUT] JDK-8196415 Disable SHA-1 Signed JARs
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 7u311,8u301,11.0.13-oracle,16.0.2
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2021-05-13
  • Updated: 2025-01-29
  • Resolved: 2021-05-17
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 11 JDK 16 JDK 17 JDK 18 JDK 7 JDK 8
11.0.12-oracleFixed 16.0.2 b05Fixed 17Fixed 18Fixed 7u311Fixed 8u301Fixed
Related Reports
CSR :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Regression issue JDK-8266971 was found, affecting performance because of changes in JDK-8196415.

Initially we did not back it out of JDK 17, so that we could try to address/reduce the performance degradation issues. However, due to time constraints, we are going to also back it out of 17, and defer addressing the performance issues to JDK 18.
Comments
Changed label to openjdk-na which is what we usually use to mark bugs as not applicable for OpenJDK backports
03-08-2021

Added jdk11u-fix-no since JDK-8196415 never got into OpenJDK 11u. Nothing to back out. The new attempt for this is JDK-8269039.
03-08-2021

Changeset: e84e1858 Author: Sean Coffey <coffeys@openjdk.org> Date: 2021-05-17 15:34:14 +0000 URL: https://git.openjdk.java.net/jdk16u/commit/e84e18580d764f612b9afaee7a470cde856a6bcc
17-05-2021

Fix Request: Performance issues reported with JDK-8196415 - opting to back out this fix for now and integrate a better solution in a later update release
17-05-2021

Thanks, I see Sean has updated the bug to make it clear. We can add 17-na label to make this clear.
13-05-2021

Why is this issue targeted to 16-pool? I would expect the main issue to be targeted to 17, then create back port issues for the older releases?
13-05-2021