Document more error codes

This commit is contained in:
Gilles Peskine 2019-07-18 13:52:30 +02:00
parent 51681556cf
commit be061337c1
2 changed files with 9 additions and 1 deletions

View file

@ -1996,6 +1996,14 @@ psa_status_t psa_cipher_update(psa_cipher_operation_t *operation,
* *
* \retval #PSA_SUCCESS * \retval #PSA_SUCCESS
* Success. * Success.
* \retval #PSA_ERROR_INVALID_ARGUMENT
* The total input size passed to this operation is not valid for
* this particular algorithm. For example, the algorithm is a based
* on block cipher and requires a whole number of blocks, but the
* total input size is not a multiple of the block size.
* \retval #PSA_ERROR_INVALID_PADDING
* This is a decryption operation for an algorithm that includes
* padding, and the ciphertext does not contain valid padding.
* \retval #PSA_ERROR_BAD_STATE * \retval #PSA_ERROR_BAD_STATE
* The operation state is not valid (not set up, IV required but * The operation state is not valid (not set up, IV required but
* not set, or already completed). * not set, or already completed).

View file

@ -149,7 +149,7 @@
* *
* \warning If a function returns this error, it is undetermined * \warning If a function returns this error, it is undetermined
* whether the requested action has completed or not. Implementations * whether the requested action has completed or not. Implementations
* should return #PSA_SUCCESS on successful completion whenver * should return #PSA_SUCCESS on successful completion whenever
* possible, however functions may return #PSA_ERROR_COMMUNICATION_FAILURE * possible, however functions may return #PSA_ERROR_COMMUNICATION_FAILURE
* if the requested action was completed successfully in an external * if the requested action was completed successfully in an external
* cryptoprocessor but there was a breakdown of communication before * cryptoprocessor but there was a breakdown of communication before