-
Bug
-
Resolution: Fixed
-
P3
-
None
This is a companion bug to JDK-8168822. I think this information needs to be done throughout our Eco-sphere, especially where admins might go looking. The term "AlgorithmConstraints" won't mean much to an admin looking to figure out why a cert with a disabled algorithm was accepted.
I looked in what I thought would be the "obvious/expected places" below, but didn't find anything. Some suggestions might be:
<java-home>/conf/security/java.security (addressed inJDK-8168822)
https://www.java.com/en/jre-jdk-cryptoroadmap.html
http://www.oracle.com/technetwork/java/javase/8u71-relnotes-2773756.html#newft
JPG blog
(i.e. an article like https://blogs.oracle.com/java-platform-group/entry/strengthening_signatures)
JSSE Ref Guide troubleshooting
CertPath (if not already there)
I looked in what I thought would be the "obvious/expected places" below, but didn't find anything. Some suggestions might be:
<java-home>/conf/security/java.security (addressed in
https://www.java.com/en/jre-jdk-cryptoroadmap.html
http://www.oracle.com/technetwork/java/javase/8u71-relnotes-2773756.html#newft
JPG blog
(i.e. an article like https://blogs.oracle.com/java-platform-group/entry/strengthening_signatures)
JSSE Ref Guide troubleshooting
CertPath (if not already there)
- duplicates
-
JDK-8168880 Document that algorithm restrictions do not apply to trusted anchors
- Closed
- relates to
-
JDK-8168822 Document that algorithm restrictions do not apply to trusted anchors
- Resolved