From c3d57f07abecb5a9737f636c279aa41324e866d4 Mon Sep 17 00:00:00 2001 From: Frank Denis Date: Tue, 8 Apr 2014 14:15:09 -0700 Subject: [PATCH] De-doxygenize crypto_verify_64.h in this branch. --- .../include/sodium/crypto_verify_64.h | 36 +------------------ 1 file changed, 1 insertion(+), 35 deletions(-) diff --git a/src/libsodium/include/sodium/crypto_verify_64.h b/src/libsodium/include/sodium/crypto_verify_64.h index fcb44e68..4835826e 100644 --- a/src/libsodium/include/sodium/crypto_verify_64.h +++ b/src/libsodium/include/sodium/crypto_verify_64.h @@ -4,54 +4,20 @@ #include #include "export.h" -/** \addtogroup strcmp - * - * @{ - */ - #define crypto_verify_64_BYTES 64U #ifdef __cplusplus extern "C" { #endif - /// @TODO SODIUM_EXPORT size_t crypto_verify_64_bytes(void); -/** - * Compares the first crypto_verify_64_BYTES of the given strings. - * - * @param[in] string1 a string - * @param[in] string2 another string - * - * @return 0 if string1 and string2 are equal, otherwise -1. - * - * @pre string1 must be minimum of crypto_verify_64_BYTES long. - * @pre string2 must be minimum of crypto_verify_64_BYTES long. - * - * @note The time taken by the function is independent of the contents - * of string1 and string2. In contrast, the standard C comparison - * function memcmp(string1,string2,64) takes time that is dependent on - * the longest matching prefix of string1 and string2. This often - * allows for easy timing attacks. - * - * Example invocation: - * - *~~~~~{.c} - * const unsigned char x[64]; - * const unsigned char y[64]; - * - * crypto_verify_64(x,y); - *~~~~~ - */ SODIUM_EXPORT int crypto_verify_64(const unsigned char *x, const unsigned char *y); -#define crypto_verify_64_ref crypto_verify_64 ///< @TODO +#define crypto_verify_64_ref crypto_verify_64 - - /// @} #ifdef __cplusplus } #endif