JDK-8215318 : Amend the Standard Algorithm Names specification to clarify that names can be defined in later versions
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 8,11,12
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-12-12
  • Updated: 2019-05-21
  • Resolved: 2019-01-18
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 12 JDK 13 JDK 8
11.0.3-oracleFixed 12 b29Fixed 13Fixed 8u211Fixed
Related Reports
CSR :  
JDK-8215320 - Amend the Standard Algorithm Names specification to clarify that names can be defined in later versions
Description
The Java Security Standard Algorithm Names specification should be amended to clarify that, as a best practice, implementations that support additional algorithms not defined in the specification can and should use the standard name of those algorithms if they are defined in later versions of the specification.

The security landscape changes at a fast pace, and new and stronger algorithms and protocols are constantly being developed and standardized.  Java SE implementations may need to add support for newer algorithms that are not defined in the Java Security Standard Algorithm Names specification for that SE version.  With this proposed change, we will clarify that implementations that support additional algorithms are recommended to use the standard name of those algorithms if they have been added to subsequent versions of the Java Security Standard Algorithm Names specification.
Comments
Thanks for confirming, Sean. [~robm], Rob, should we remove "jdk11u-fix-request jdk11u-fix-yes" tags from this issue then, as it does not affect OpenJDK Update project? It would get the issue off our backporting radar.
21-02-2019
[~shade] That is correct.
19-02-2019
Looking at public review thread, am I right this affects only closed/src/java.base/share/specs/security/standard-names.md, and as such does not affect OpenJDK code? There is no standard-names.md in jdk-updates/jdk11u.
19-02-2019
Fix Request Requesting approval to push to 11u. This is one of the changes proposed for the Java SE Maintenance Review. This change is a clarification to the Java Security Standard Algorithm Names specification to allow implementations to support names that are defined in later revisions. The change is low risk (docs only). The patch has already been applied to JDK 12 and is identical for 11u. The CSR has already been approved for 11 and 12. The public code review thread for the JDK 12 patch is at: https://mail.openjdk.java.net/pipermail/security-dev/2019-January/019114.html
28-01-2019