| commit | 6a87d7f37462fe33d0da8b730ce7f81e31063790 | |
| author | eroman <eroman@chromium.org> | |
| Wed, 14 Jan 2015 22:32:00 +0000 (14 14:32 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 14 Jan 2015 22:32:48 +0000 (14 22:32 +0000) | ||
| tree | 64a193f0e4c7608c0f91006eb28d3e5dc4d3f02f | treesnapshot (tar.gz zip) |
| parent | b081bab860ed0b74824c7e6a268d7699b61541fc | commitdiff |
Change the WebCrypto behavior when exporting EC private keys that were imported without a public key.
Before such keys were exported to PKCS8 format, the publicKey would be missing in the ECPrivateKey.
Now instead the publicKey is written to exported bytes even if it was not provided during import.
This is more consistent with how export works for JWK, where the public key is a required parameter.
It also speeds up the structured (de) cloning of such keys, which uses PKCS8 format under the hood (and for which if the publicKey was not provided, BoringSSL computes it).
BUG=445635
Review URL: https://codereview.chromium.org/835633002
Cr-Commit-Position: refs/heads/master@{#311553}
Before such keys were exported to PKCS8 format, the publicKey would be missing in the ECPrivateKey.
Now instead the publicKey is written to exported bytes even if it was not provided during import.
This is more consistent with how export works for JWK, where the public key is a required parameter.
It also speeds up the structured (de) cloning of such keys, which uses PKCS8 format under the hood (and for which if the publicKey was not provided, BoringSSL computes it).
BUG=445635
Review URL: https://codereview.chromium.org/835633002
Cr-Commit-Position: refs/heads/master@{#311553}