JDK-8156674 : Non-ASCII code in java.security
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Priority: P2
- Status: Resolved
- Resolution: Duplicate
- Submitted: 2016-05-10
- Updated: 2016-05-19
- Resolved: 2016-05-19
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.
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 9 |
|---|
9Resolved  |
Related Reports
|
Duplicate :
|
Description
There are a few non-ASCII code presented in java.security in the update of JDK-8140422. http://hg.openjdk.java.net/jdk9/dev/jdk/rev/8fc301b7b8f8 +# "CertConstraint" specifies additional constraints for +# certificates that contain algorithms that are restricted: +# +# �� �� "jdkCA" prohibits the specified algorithm only if the algorithm is used +# �� �� �� �� in a certificate chain that terminates at a marked trust anchor in the +# �� �� �� �� lib/security/cacerts keystore. �� All other chains are not affected. +# �� �� �� �� If the jdkCA constraint is not set, then all chains using the +# �� �� �� �� specified algorithm are restricted. jdkCA may only be used once in +# a DisabledAlgorithm expression. +# �� �� �� �� Example: �� To apply this constraint to SHA-1 certificates, include +# �� �� �� �� the following: �� "SHA1 jdkCA" +#
Comments
|