-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
b16
For example, the following setting:
jdk.crypto.disabledAlgorithms=MessageDigest.MD2
would result in a NoSuchAlgorithmException if code called MessageDigest.getInstance("MD2"), even if a configured provider supported MD2. It would also apply to the getInstance methods that have a provider argument.
- causes
-
JDK-8367583 sun/security/util/AlgorithmConstraints/InvalidCryptoDisabledAlgos.java fails after JDK-8244336
-
- Resolved
-
- csr for
-
JDK-8364386 Restrict algorithms at JCE layer
-
- Closed
-
- duplicates
-
JDK-8360146 Add system/security property to disable RSAES-PKCS-v1_5 padding
-
- Closed
-
- relates to
-
JDK-8315487 Security Providers Filter
-
- In Progress
-
-
JDK-8361964 Remove outdated algorithms from requirements and add PBES2 algorithms
-
- Resolved
-
-
JDK-8254711 Add java.security.Provider.getService JFR Event
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/35dabb1a
-
Review(master) openjdk/jdk/26377