-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b63
-
generic, sparc
-
generic, solaris_9
Paragraph 2 of Appendix A of the JCE reference guide (http://java.sun.com/j2se/1.5.0/docs/guide/security/jce/JCERefGuide.html#AppA)states:
In some cases naming conventions are suggested for forming names that are not explicitly listed, to facilitate name consistency across provider implementations. Such suggestions use items in angle brackets (such as <digest> and <encryption>) as placeholders to be replaced by specific message digest, encryption algorithm, and other names.
The above language states that the naming conventions for forming names such as PBEWith<digest>And<encryption> or PBEWith<prf>And<encryption> are suggestions, not requirements.
The above text should be changed to make it clear that the naming conventions are requirements, not recommendations.
In some cases naming conventions are suggested for forming names that are not explicitly listed, to facilitate name consistency across provider implementations. Such suggestions use items in angle brackets (such as <digest> and <encryption>) as placeholders to be replaced by specific message digest, encryption algorithm, and other names.
The above language states that the naming conventions for forming names such as PBEWith<digest>And<encryption> or PBEWith<prf>And<encryption> are suggestions, not requirements.
The above text should be changed to make it clear that the naming conventions are requirements, not recommendations.
- duplicates
-
JDK-6332761 PBE SecretKeys are hard coded to return PBEWithMD5AndDES regardless of factory algorithm.
-
- Closed
-