Leave behaviour on NULL buffers to SHA-1 unspecified for now

We deal correctly with NULL being passed alongside a zero length
argument, but don't have tests for it, so we shouldn't promise
that it works.
This commit is contained in:
Hanno Becker 2018-12-18 15:42:53 +00:00
parent b3906d8829
commit 9171c6e9ec

View file

@ -141,7 +141,6 @@ int mbedtls_sha1_starts_ret( mbedtls_sha1_context *ctx );
* and have a hash operation started.
* \param input The buffer holding the input data.
* This must be a readable buffer of length \p ilen Bytes.
* It may be \c NULL if \p ilen is zero.
* \param ilen The length of the input data \p input in Bytes.
*
* \return \c 0 on success.
@ -224,7 +223,6 @@ MBEDTLS_DEPRECATED void mbedtls_sha1_starts( mbedtls_sha1_context *ctx );
* have a hash operation started.
* \param input The buffer holding the input data.
* This must be a readable buffer of length \p ilen Bytes.
* It may be \c NULL if \p ilen is zero.
* \param ilen The length of the input data \p input in Bytes.
*
*/
@ -286,7 +284,6 @@ MBEDTLS_DEPRECATED void mbedtls_sha1_process( mbedtls_sha1_context *ctx,
*
* \param input The buffer holding the input data.
* This must be a readable buffer of length \p ilen Bytes.
* It may be \c NULL if \p ilen is zero.
* \param ilen The length of the input data \p input in Bytes.
* \param output The SHA-1 checksum result.
* This must be a writable buffer of length \c 20 Bytes.
@ -322,7 +319,6 @@ int mbedtls_sha1_ret( const unsigned char *input,
*
* \param input The buffer holding the input data.
* This must be a readable buffer of length \p ilen Bytes.
* It may be \c NULL if \p ilen is zero.
* \param ilen The length of the input data \p input in Bytes.
* \param output The SHA-1 checksum result. This must be a writable
* buffer of size \c 20 Bytes.