-
Bug
-
Resolution: Fixed
-
P1
-
6u10, 7
-
b12
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2215631 | 8 | Vincent Ryan | P2 | Closed | Fixed | b12 |
| JDK-8043634 | 6u85 | Mala Bankal | P1 | Closed | Fixed | b02 |
| JDK-8044757 | 5.0u75 | Mala Bankal | P1 | Closed | Not an Issue |
The fix for CR 7054637 introduced a PKCS11 token attribute to control whether an EC point encoding is wrapped in an ASN.1 OCTET STRING or not.
It has been reported that the numeric identifier chosen for that attribute will clash with
the identifier already chosen by a vendor of PKCS11 tokens as a vendor extension.
To avoid this and any future namespace collisions from other token vendors a JCE provider
attribute should be used instead of a token attribute.
It has been reported that the numeric identifier chosen for that attribute will clash with
the identifier already chosen by a vendor of PKCS11 tokens as a vendor extension.
To avoid this and any future namespace collisions from other token vendors a JCE provider
attribute should be used instead of a token attribute.
- backported by
-
JDK-8043634 Use a PKCS11 config attribute to control encoding of an EC point
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
(1 relates to)