From 8cbb048c3ea416f2bd8a3706d027f3aa26ef08d9 Mon Sep 17 00:00:00 2001 From: Adam Eijdenberg Date: Mon, 19 Oct 2015 11:16:25 -0700 Subject: [PATCH] Clarify return values for EVP_DigestVerifyFinal. Previous language was unclear. New language isn't pretty but I believe it is more accurate. Signed-off-by: Rich Salz Reviewed-by: Ben Laurie Reviewed-by: Richard Levitte --- doc/crypto/EVP_DigestVerifyInit.pod | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/crypto/EVP_DigestVerifyInit.pod b/doc/crypto/EVP_DigestVerifyInit.pod index 44d3cdbb0d..338fc74616 100644 --- a/doc/crypto/EVP_DigestVerifyInit.pod +++ b/doc/crypto/EVP_DigestVerifyInit.pod @@ -36,10 +36,11 @@ B of length B. EVP_DigestVerifyInit() and EVP_DigestVerifyUpdate() return 1 for success and 0 for failure. -Unlike other functions the return value 0 from EVP_DigestVerifyFinal() only -indicates that the signature did not verify successfully (that is tbs did -not match the original data or the signature was of invalid form) it is not an -indication of a more serious error. +EVP_DigestVerifyFinal() returns 1 for success; any other value indicates +failure. A return value of zero indicates that the signature did not verify +successfully (that is, tbs did not match the original data or the signature had +an invalid form), while other values indicate a more serious error (and +sometimes also indicate an invalid signature form). The error codes can be obtained from L. -- 2.25.1