You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on the provider and how they use ECC keys, it might be useful to have a way to parse the ECC key pairs. This is specially useful for the ImportKey/ExportKey operations.
We are using the picky crates to do ASN.1 parsing/serialization and before we were also defining our own ASN.1 types, like for RSA keys. See #201 for example.
As an initial step, we should make a PR to add support for ECPrivateKey in picky-asn1-x509 crate.
The text was updated successfully, but these errors were encountered:
Depending on the provider and how they use ECC keys, it might be useful to have a way to parse the ECC key pairs. This is specially useful for the ImportKey/ExportKey operations.
See this comment for details:
For the ECC key pairs, the format is explained here and is the ASN.1 type
ECPrivateKey
:We are using the
picky
crates to do ASN.1 parsing/serialization and before we were also defining our own ASN.1 types, like for RSA keys. See #201 for example.As an initial step, we should make a PR to add support for
ECPrivateKey
inpicky-asn1-x509
crate.The text was updated successfully, but these errors were encountered: