-
Bug
-
Resolution: Fixed
-
P4
-
10
-
b13
-
Not verified
We need to backout JDK-8182143 because of possible issues on Windows although we don't have a test to reproduce it. See the following email thread
http://mail.openjdk.java.net/pipermail/security-dev/2017-June/016005.html
The following code which were removed inJDK-8182143 looks like a hack
http://hg.openjdk.java.net/jdk9/dev/jdk/file/82ed25c3cea9/src/java.base/share/classes/sun/security/ssl/SignatureAndHashAlgorithm.java#l415
I think the root cause is crypto key incompatibility, seeJDK-8182386
http://mail.openjdk.java.net/pipermail/security-dev/2017-June/016005.html
The following code which were removed in
http://hg.openjdk.java.net/jdk9/dev/jdk/file/82ed25c3cea9/src/java.base/share/classes/sun/security/ssl/SignatureAndHashAlgorithm.java#l415
I think the root cause is crypto key incompatibility, see
- relates to
-
JDK-8182386 Crypto keys should be compatible between security providers
- Closed
-
JDK-8182143 SHA224-based signature algorithms are not enabled for TLSv12 on Windows
- Closed