-
Bug
-
Resolution: Fixed
-
P3
-
8, 11, 14
-
b30
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8236788 | 15 | Weijun Wang | P3 | Resolved | Fixed | b05 |
JDK-8246367 | 13.0.4 | Weijun Wang | P3 | Resolved | Fixed | b04 |
JDK-8243092 | 11.0.8 | Weijun Wang | P3 | Resolved | Fixed | b01 |
JDK-8239050 | openjdk8u252 | Bradford Wetmore | P3 | Resolved | Fixed | b03 |
JDK-8238068 | 8u261 | Bradford Wetmore | P3 | Resolved | Fixed | b01 |
JDK-8238802 | 8u251 | Bradford Wetmore | P3 | Resolved | Fixed | b04 |
JDK-8246939 | emb-8u261 | Bradford Wetmore | P3 | Resolved | Fixed | team |
JDK-8239745 | emb-8u251 | Bradford Wetmore | P3 | Resolved | Fixed | team |
0238:001A [1] SEQUENCE
023A:0009 [10] OID 1.2.840.10045.4.3 (ecdsaWithSpecified)
0243:000F [11] SEQUENCE
0245:000B [110] OID 2.16.840.1.101.3.4.2.2 (sha-384)
0250:0002 [111] NULL
The parameters here is treated as an EC parameter (normally used to specify a named curve) and an exception will be thrown.
An earlier draft of ECDSA at https://tools.ietf.org/html/draft-ietf-pkix-sha2-dsa-ecdsa-04#section-3.2.3 mentioned it with "Conforming CA implementations MUST NOT specify the ecdsa-with-Specified OID when encoding certificates and CRLs" and suggested "conforming client implementations MAY recognize" it, but even this line was removed in the final version at https://tools.ietf.org/html/rfc5758 and this OID is never documented anywhere.
- backported by
-
JDK-8236788 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8238068 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8238802 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8239050 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8239745 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8243092 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8246367 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-
-
JDK-8246939 Deal with ECDSA using ecdsa-with-SHA2 plus hash algorithm as AlgorithmId
-
- Resolved
-