Document key usage for GenerateCertificateKeyPair
bug: 277124807 Merged from https://widevine-internal-review.googlesource.com/177958 Change-Id: I867d664a73ceba7391b5054365c4352a7c6aa301
This commit is contained in:
committed by
Robert Shih
parent
bf5804a103
commit
0a9bc6534c
@@ -4916,6 +4916,14 @@ OEMCryptoResult OEMCrypto_GetBootCertificateChain(
|
||||
* key is an ECC key, then |public_key_signature| is the ASN.1 DER-encoded (R,S)
|
||||
* signature as specified in RFC 3279 2.2.3.
|
||||
*
|
||||
* After this function completes successfully, the session will hold a private
|
||||
* key and will be ready for a call to
|
||||
* OEMCrypto_PrepAndSignProvisioningRequest(). In particular, when this
|
||||
* function is used to generate a DRM Certificate key pair, the session will be
|
||||
* ready to sign a provisioning request with the DRM Cert private key. When this
|
||||
* function is used to generate an OEM Certificate key pair, the session will be
|
||||
* ready to sign a provisioning request with the OEM Cert private key.
|
||||
*
|
||||
* @param[in] session: session id.
|
||||
* @param[out] public_key: pointer to the buffer that receives the public key
|
||||
* that is to be certified by the server. The key must be an ASN.1
|
||||
|
||||
Reference in New Issue
Block a user