Remove get_output_size() method from keymaster HAL.
Rather than requiring implementations to be able to predict output sizes, we'll just have the Java layer make a very conservative guess. Change-Id: I4ef53a09d122d4ecf0c80b9dadc9c7a9073561cc
This commit is contained in:
parent
41e91e9fa3
commit
e57b65c454
1 changed files with 0 additions and 12 deletions
|
@ -555,18 +555,6 @@ struct keymaster_device {
|
||||||
size_t* out_params_count,
|
size_t* out_params_count,
|
||||||
keymaster_operation_handle_t* operation_handle);
|
keymaster_operation_handle_t* operation_handle);
|
||||||
|
|
||||||
/**
|
|
||||||
* Get an estimate of the output that will be generated by calling update() with the specified
|
|
||||||
* number of input bytes, followed by finish(). The estimate may not be exact, but is
|
|
||||||
* guaranteed not to be smaller than sum of the output lengths from update() and finish(). The
|
|
||||||
* estimate takes into account input data already provided.
|
|
||||||
*
|
|
||||||
* \param[in] input_length The number of additional input bytes to be processed.
|
|
||||||
*
|
|
||||||
* \param[out] output_estimate The length of the output that will be produced.
|
|
||||||
*/
|
|
||||||
keymaster_error_t (*get_output_size)(size_t input_length, size_t* output_estimate);
|
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* Provides data to, and possibly receives output from, an ongoing cryptographic operation begun
|
* Provides data to, and possibly receives output from, an ongoing cryptographic operation begun
|
||||||
* with begin().
|
* with begin().
|
||||||
|
|
Loading…
Reference in a new issue