tests/data_files/ec_prv.pk8param.der

0<EFBFBD><EFBFBD>0*<2A>H<EFBFBD>=*<2A>H<EFBFBD>=y0w <20><><EFBFBD><EFBFBD>_<EFBFBD>1<EFBFBD>3<EFBFBD><33>da<64><61>V<EFBFBD>\<5C><>6!<21>hk<68><02>O<EFBFBD><4F>
*<2A>H<EFBFBD>=<07>DBd%q<>.<2E><>z<EFBFBD>	<09><>(e
"<22>%k<>1D<31>ǿ}<7D>]<5D>4<EFBFBD><1E>9<EFBFBD>5<EFBFBD>/<2F>w@B7<>f[Mez7+x<>Z<EFBFBD>.7<>'
Fix parsing of PKCS#8 encoded Elliptic Curve keys. The relevant ASN.1 definitions for a PKCS#8 encoded Elliptic Curve key are: PrivateKeyInfo ::= SEQUENCE { version Version, privateKeyAlgorithm PrivateKeyAlgorithmIdentifier, privateKey PrivateKey, attributes [0] IMPLICIT Attributes OPTIONAL } AlgorithmIdentifier ::= SEQUENCE { algorithm OBJECT IDENTIFIER, parameters ANY DEFINED BY algorithm OPTIONAL } ECParameters ::= CHOICE { namedCurve OBJECT IDENTIFIER -- implicitCurve NULL -- specifiedCurve SpecifiedECDomain } ECPrivateKey ::= SEQUENCE { version INTEGER { ecPrivkeyVer1(1) } (ecPrivkeyVer1), privateKey OCTET STRING, parameters [0] ECParameters {{ NamedCurve }} OPTIONAL, publicKey [1] BIT STRING OPTIONAL } Because of the two optional fields, there are 4 possible variants that need to be parsed: no optional fields, only parameters, only public key, and both optional fields. Previously mbedTLS was unable to parse keys with "only parameters". Also, only "only public key" was tested. There was a test for "no optional fields", but it was labelled incorrectly as SEC.1 and not run because of a great renaming mixup. 2018-02-16 13:11:04 -08:00				`0<EFBFBD><EFBFBD>0<2A>H<EFBFBD>=<2A>H<EFBFBD>=y0w <20><><EFBFBD><EFBFBD>_<EFBFBD>1<EFBFBD>3<EFBFBD><33>da<64><61>V<EFBFBD>\<5C><>6!<21>hk<68><02>O<EFBFBD><4F>`
				`*<2A>H<EFBFBD>=<07>DBd%q<>.<2E><>z<EFBFBD> <09><>(e "<22>%k<>1D<31>ǿ}<7D>]<5D>4<EFBFBD><1E>9<EFBFBD>5<EFBFBD>/<2F>w@B7<>f[Mez7+x<>Z<EFBFBD>.7<>'`