EVP_DIGESTVERIFYINIT(3)
okay bestie, this is the EVP_DIGESTVERIFYINIT(3) page from the Library Functions Manual β yes, the libcrypto one. Buckle up, weβre doing signature verification and itβs actually iconic π β¨
π NAME π
EVP_DigestVerifyInit, EVP_DigestVerifyUpdate, EVP_DigestVerifyFinal, EVP_DigestVerify β EVP signature verification functions π«Ά
β¨ SYNOPSIS β¨
library βlibcryptoβ #include <openssl/evp.h>
int
EVP_DigestVerifyInit(EVP_MD_CTX *ctx, EVP_PKEY_CTX **pctx,
const EVP_MD *type, ENGINE *engine, EVP_PKEY *pkey);
int
EVP_DigestVerifyUpdate(EVP_MD_CTX *ctx, const void *d, size_t cnt);
int
EVP_DigestVerifyFinal(EVP_MD_CTX *ctx, const unsigned char *sig,
size_t siglen);
int
EVP_DigestVerify(EVP_MD_CTX *ctx, const unsigned char *sig,
size_t siglen, const unsigned char *tbs, size_t *tbslen);
π¦ DESCRIPTION π¦
so the EVP signature routines are basically a high-level interface to digital signatures β main character energy, no cap π₯
EVP_DigestVerifyInit() sets up the verification context ctx to use the digest type and the public key pkey. Before you call this function, obtain ctx from EVP_MD_CTX_new(3) or call EVP_MD_CTX_reset(3) on it. The engine argument is always ignored and passing NULL is recommended β so yeah, NULL it and move on bestie π
If pctx is not NULL, any pointer passed in as *pctx is ignored and overwritten by an internal pointer to the EVP_PKEY_CTX used by the verification operation: this can be used to set alternative signing options. The returned EVP_PKEY_CTX must not be freed by the application. It is freed automatically when the EVP_MD_CTX is freed. so do not touch it, periodt π
EVP_DigestVerifyUpdate() hashes cnt bytes of data at d into the verification context ctx. This function can be called several times on the same ctx to include additional data. This function is currently implemented using a macro β cute, lowkey π
EVP_DigestVerifyFinal() verifies the data in ctx against the signature in sig of length siglen. yes queen, check that signature π
EVP_DigestVerify() verifies tbslen bytes at tbs against the signature in sig of length siglen. EVP_DigestVerify() is a one shot operation which verifies a single block of data in one function call. For algorithms that support streaming it is equivalent to calling EVP_DigestVerifyUpdate() and EVP_DigestVerifyFinal(). one-and-done vibes β¨
The EVP interface to digital signatures should almost always be used in preference to the low-level interfaces. This is because the code then becomes transparent to the algorithm used and much more flexible. itβs giving βwrite once, slay everywhereβ π
The call to EVP_DigestVerifyFinal() internally finalizes a copy of the digest context. This means that EVP_VerifyUpdate(3) and EVP_VerifyFinal(3) can be called later to digest and verify additional data. yes, those are the exact names from the original β keep them exactly as written, iykyk π
Since only a copy of the digest context is ever finalized, the context must be cleaned up after use by calling EVP_MD_CTX_free(3) or a memory leak will occur.
bestie, fr fr: clean up with EVP_MD_CTX_free(3) or you get a memory leak. no cap, thatβs the warning π
πΈ RETURN VALUES πΈ
EVP_DigestVerifyInit() and EVP_DigestVerifyUpdate() return 1 for success and 0 for failure. simple enough π«Ά
EVP_DigestVerifyFinal() and EVP_DigestVerify() return 1 for success; any other value indicates failure. A return value of 0 indicates that the signature did not verify successfully (that is, the signature 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). so 0 is βnope, bad signature vibesβ and other values are βbigger yikesβ π
The error codes can be obtained from ERR_get_error(3). go get the receipts π
π SEE ALSO π
evp(3), EVP_DigestInit(3), EVP_DigestSignInit(3) β the squad π
π HISTORY π
EVP_DigestVerifyInit(), EVP_DigestVerifyUpdate(), and EVP_DigestVerifyFinal() first appeared in OpenSSL 1.0.0 and have been available since OpenBSD 4.9. vintage but still serving π
EVP_DigestVerify() first appeared in OpenSSL 1.1.1 and have been available since OpenBSD 7.0. newer icon behavior β
mwah π this page came from Debian, dated June 8, 2025, and it lives under EVP_DIGESTVERIFYINIT(3) β slay and verify responsibly πβ¨
π¦ where this page comes from
- alpine 3.24: libressl-doc 4.3.1-r0 Β· custom
- arch rolling: libressl 4.4.0-1 Β· ISC AND custom:OpenSSL
- Copyright (c) 2006, 2009, 2014, 2015, 2016, 2017 The OpenSSL Project
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms