-
Bug
-
Resolution: Fixed
-
P2
-
5.0
-
b130
-
sparc
-
solaris_9
-
Verified
The API specifications for java.security, java.security.cert, and javax.crypto packages do not specify requirements for security algorithms and algorithm-specific requirements (e.g. encryption strength).
This issue makes it difficult to develop conformance tests. In an extreme case, an implementation can use very weak algorithms and still be considered a valid implementation according to the current javadoc API specification.
Furthermore, there is currently no guarantee that applications can interoperate. We need to specify a minimum level of required algorithms and parameters that all JRE implementations must support. This will improve interoperability and guarantee a minimum set of algorithms that all Java applications can depend on.
This issue makes it difficult to develop conformance tests. In an extreme case, an implementation can use very weak algorithms and still be considered a valid implementation according to the current javadoc API specification.
Furthermore, there is currently no guarantee that applications can interoperate. We need to specify a minimum level of required algorithms and parameters that all JRE implementations must support. This will improve interoperability and guarantee a minimum set of algorithms that all Java applications can depend on.
- relates to
-
JDK-7022467 SecretKeyFactory doesn't support algorithm "AES" on Windows and Linux
-
- Closed
-
-
JDK-6676054 Java provider SunPKCS11-Solaris doesn't support KeyPairGenerator with DSA alg. for solaris 10 11
-
- Closed
-
-
JDK-8283795 Add TLSv1.3 and CNSA 1.0 algorithms to implementation requirements
-
- Resolved
-