-
Bug
-
Resolution: Fixed
-
P4
-
21
-
None
-
b06
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8369789 | 21.0.11-oracle | Oumaiyma Intissar | P4 | Open | Unresolved | |
| JDK-8369790 | 25-pool | Oumaiyma Intissar | P4 | Open | Unresolved |
The javadoc of javax.crypto.Cipher class specifies:
A transformation is of the form:
"algorithm/mode/padding" or
"algorithm"
(in the latter case, provider-specific default values for the mode and padding scheme are used).
Thus, we should reject transformations in "algorithm/mode/padding" syntax with empty mode and/or padding.
A transformation is of the form:
"algorithm/mode/padding" or
"algorithm"
(in the latter case, provider-specific default values for the mode and padding scheme are used).
Thus, we should reject transformations in "algorithm/mode/padding" syntax with empty mode and/or padding.
- backported by
-
JDK-8369789 Stricter checking for cipher transformations
-
- Open
-
-
JDK-8369790 Stricter checking for cipher transformations
-
- Open
-
- caused by
-
JDK-8288050 Add support of SHA-512/224 and SHA-512/256 to the PBKDF2 and PBES2 impls in SunJCE provider
-
- Resolved
-
- relates to
-
JDK-8358159 Empty mode/padding in cipher transformations
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/ec7c6be6
-
Review(master)
openjdk/jdk/25808
(1 links to)