-
Bug
-
Resolution: Fixed
-
P3
-
6
-
None
-
beta
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2132433 | 5.0u7 | Bradford Wetmore | P3 | Resolved | Fixed | b01 |
Currently, JCE framework would convert all algorithm names to uppercases
when parsing the jurisdiction policy file. However, Cipher class stores
the user specified transformation directly and uses it to look up the
granted crypto permission. This has not been an issue since most algorithm
names in JCE are in uppercases by convention and has the same keysize
limit as the default (wildcard) one.
However, DESede has a mixed case name, thus the current JCE crypto
permission lookup fails to find the right permission and use the
default one instead.
###@###.### 2005-2-15 22:37:21 GMT
when parsing the jurisdiction policy file. However, Cipher class stores
the user specified transformation directly and uses it to look up the
granted crypto permission. This has not been an issue since most algorithm
names in JCE are in uppercases by convention and has the same keysize
limit as the default (wildcard) one.
However, DESede has a mixed case name, thus the current JCE crypto
permission lookup fails to find the right permission and use the
default one instead.
###@###.### 2005-2-15 22:37:21 GMT
- backported by
-
JDK-2132433 Crypto permission lookup is wrong when the Cipher algorithm name is not all uppercase
-
- Resolved
-