Difference between revisions of "EVP Signing and Verifying"
Line 1: | Line 1: | ||
There are two APIs available to perform sign and verify operations. The first are the older <tt>EVP_Sign*</tt> and <tt>EVP_Verify*</tt> functions; and the second are the newer and more flexible <tt>EVP_DigestSign*</tt> and <tt>EVP_DigestVerify*</tt> functions. Though the APIs are similar, new applications should use the <tt>EVP_DigestSign*</tt> and <tt>EVP_DigestVerify*</tt> functions. | There are two APIs available to perform sign and verify operations. The first are the older <tt>EVP_Sign*</tt> and <tt>EVP_Verify*</tt> functions; and the second are the newer and more flexible <tt>EVP_DigestSign*</tt> and <tt>EVP_DigestVerify*</tt> functions. Though the APIs are similar, new applications should use the <tt>EVP_DigestSign*</tt> and <tt>EVP_DigestVerify*</tt> functions. | ||
− | The examples below use the new <tt>EVP_DigestSign*</tt> and <tt>EVP_DigestVerify*</tt> functions to demonstarte signing and verification. The first example uses an HMAC, and the second example uses RSA key pairs. Additionally, the code for the | + | The examples below use the new <tt>EVP_DigestSign*</tt> and <tt>EVP_DigestVerify*</tt> functions to demonstarte signing and verification. The first example uses an HMAC, and the second example uses RSA key pairs. Additionally, the code for the examples are available for download. |
==Overview== | ==Overview== |
Revision as of 01:25, 8 February 2015
There are two APIs available to perform sign and verify operations. The first are the older EVP_Sign* and EVP_Verify* functions; and the second are the newer and more flexible EVP_DigestSign* and EVP_DigestVerify* functions. Though the APIs are similar, new applications should use the EVP_DigestSign* and EVP_DigestVerify* functions.
The examples below use the new EVP_DigestSign* and EVP_DigestVerify* functions to demonstarte signing and verification. The first example uses an HMAC, and the second example uses RSA key pairs. Additionally, the code for the examples are available for download.
Overview
In general, signing a message is a three stage process:
- Initialize the context with a message digest/hash function and EVP_PKEY key
- Add the message data (this step can be repeated as many times as necessary)
- Finalize the context to create the signature
In order to initialize, you first need to select a message digest algorithm (refer to Working with Algorithms and Modes). Second, you need to provide a EVP_PKEY containing a key for an algorithm that supports signing (refer to Working with EVP_PKEYs). Both the digest and the key are provided to EVP_DigestSignInit.
To add the message data, you call EVP_DigestSignUpdate one or more times.
To finalize the operation and retrieve the signature, you call EVP_DigestSignFinal.
In general, verification follows the same steps. The key difference is the finalization:
- Initialize the context with a message digest/hash function and EVP_PKEY key
- Add the message data (this step can be repeated as many times as necessary)
- Finalize the context with the previous signature to verify the message
When finalizing during verification, you add the signature in the call. EVP_DigestVerifyFinal will then perform the validate the signature on the message.
HMAC
The first example shows how to create a signature over a message using an HMAC with EVP_DigestSignInit, EVP_DigestSignUpdate and EVP_DigestSignFinal. The second part shows how to verify a signature over the message using using the same EVP_DigestSign functions. You do not use the EVP_DigestVerify functions to verify.
Note well: you do not use EVP_DigestVerify to verify an HMAC. EVP_DigestVerifyInit will fail with an error 0x608f096: error:0608F096:digital envelope routines:EVP_PKEY_verify_init:operation not supported for this keytype.
Signing
The code below signs a string using an HMAC.
int sign_it(const byte* msg, size_t mlen, byte** sig, size_t* slen, EVP_PKEY* pkey) { /* Returned to caller */ int result = -1; if(!msg || !mlen || !sig || !pkey) { assert(0); return -1; } if(*sig) OPENSSL_free(*sig); *sig = NULL; *slen = 0; EVP_MD_CTX* ctx = NULL; do { ctx = EVP_MD_CTX_create(); assert(ctx != NULL); if(ctx == NULL) { printf("EVP_MD_CTX_create failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } const EVP_MD* md = EVP_get_digestbyname("SHA256"); assert(md != NULL); if(md == NULL) { printf("EVP_get_digestbyname failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } int rc = EVP_DigestInit_ex(ctx, md, NULL); assert(rc == 1); if(rc != 1) { printf("EVP_DigestInit_ex failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } rc = EVP_DigestSignInit(ctx, NULL, md, NULL, pkey); assert(rc == 1); if(rc != 1) { printf("EVP_DigestSignInit failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } rc = EVP_DigestSignUpdate(ctx, msg, mlen); assert(rc == 1); if(rc != 1) { printf("EVP_DigestSignUpdate failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } size_t req = 0; rc = EVP_DigestSignFinal(ctx, NULL, &req); assert(rc == 1); if(rc != 1) { printf("EVP_DigestSignFinal failed (1), error 0x%lx\n", ERR_get_error()); break; /* failed */ } assert(req > 0); if(!(req > 0)) { printf("EVP_DigestSignFinal failed (2), error 0x%lx\n", ERR_get_error()); break; /* failed */ } *sig = OPENSSL_malloc(req); assert(*sig != NULL); if(*sig == NULL) { printf("OPENSSL_malloc failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } *slen = req; rc = EVP_DigestSignFinal(ctx, *sig, slen); assert(rc == 1); if(rc != 1) { printf("EVP_DigestSignFinal failed (3), return code %d, error 0x%lx\n", rc, ERR_get_error()); break; /* failed */ } assert(req == *slen); if(rc != 1) { printf("EVP_DigestSignFinal failed, mismatched signature sizes %ld, %ld", req, *slen); break; /* failed */ } result = 0; } while(0); if(ctx) { EVP_MD_CTX_destroy(ctx); ctx = NULL; } /* Convert to 0/1 result */ return !!result; }
Verifying
The code below performs verification of a string using an HMAC.
int verify_it(const byte* msg, size_t mlen, const byte* sig, size_t slen, EVP_PKEY* pkey) { /* Returned to caller */ int result = -1; if(!msg || !mlen || !sig || !slen || !pkey) { assert(0); return -1; } EVP_MD_CTX* ctx = NULL; do { ctx = EVP_MD_CTX_create(); assert(ctx != NULL); if(ctx == NULL) { printf("EVP_MD_CTX_create failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } const EVP_MD* md = EVP_get_digestbyname("SHA256"); assert(md != NULL); if(md == NULL) { printf("EVP_get_digestbyname failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } int rc = EVP_DigestInit_ex(ctx, md, NULL); assert(rc == 1); if(rc != 1) { printf("EVP_DigestInit_ex failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } rc = EVP_DigestSignInit(ctx, NULL, md, NULL, pkey); assert(rc == 1); if(rc != 1) { printf("EVP_DigestSignInit failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } rc = EVP_DigestSignUpdate(ctx, msg, mlen); assert(rc == 1); if(rc != 1) { printf("EVP_DigestSignUpdate failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } byte buff[EVP_MAX_MD_SIZE]; size_t size = sizeof(buff); rc = EVP_DigestSignFinal(ctx, buff, &size); assert(rc == 1); if(rc != 1) { printf("EVP_DigestVerifyFinal failed, error 0x%lx\n", ERR_get_error()); break; /* failed */ } assert(size > 0); if(!(size > 0)) { printf("EVP_DigestSignFinal failed (2)\n"); break; /* failed */ } const size_t m = (slen < size ? slen : size); result = !!CRYPTO_memcmp(sig, buff, m); OPENSSL_cleanse(buff, sizeof(buff)); } while(0); if(ctx) { EVP_MD_CTX_destroy(ctx); ctx = NULL; } /* Convert to 0/1 result */ return !!result; }
Public Key
The second example shows how to create a signature over a message using public keys with EVP_DigestSignInit, EVP_DigestSignUpdate and EVP_DigestSignFinal. The second example shows how to verify a signature over the message using EVP_DigestVerifyInit, EVP_DigestVerifyUpdate and EVP_DigestVerifyFinal. Unlike HMACs, you do use the EVP_DigestVerify functions to verify.
Signing
EVP_MD_CTX *mdctx = NULL; int ret = 0; *sig = NULL; /* Create the Message Digest Context */ if(!(mdctx = EVP_MD_CTX_create())) goto err; /* Initialise the DigestSign operation - SHA-256 has been selected as the message digest function in this example */ if(1 != EVP_DigestSignInit(mdctx, NULL, EVP_sha256(), NULL, key)) goto err; /* Call update with the message */ if(1 != EVP_DigestSignUpdate(mdctx, msg, strlen(msg))) goto err; /* Finalise the DigestSign operation */ /* First call EVP_DigestSignFinal with a NULL sig parameter to obtain the length of the * signature. Length is returned in slen */ if(1 != EVP_DigestSignFinal(mdctx, NULL, slen)) goto err; /* Allocate memory for the signature based on size in slen */ if(!(*sig = OPENSSL_malloc(sizeof(unsigned char) * (*slen)))) goto err; /* Obtain the signature */ if(1 != EVP_DigestSignFinal(mdctx, *sig, slen)) goto err; /* Success */ ret = 1; err: if(ret != 1) { /* Do some error handling */ } /* Clean up */ if(*sig && !ret) OPENSSL_free(*sig); if(mdctx) EVP_MD_CTX_destroy(mdctx);
Note: There is no difference in the API between signing using an asymmetric algorithm, and generating a MAC code. In the case of CMAC no message digest function is required (NULL can be passed). Signing using the EVP_Sign* functions is very similar to the above example, except there is no support for MAC codes. Note that CMAC is only supported in the (as yet unreleased) version 1.1.0 of OpenSSL.
Refer to Manual:EVP_DigestSignInit(3) for further details on the EVP_DigestSign* functions, and Manual:EVP_SignInit(3) for the EVP_Sign* functions.
Verifying
Verifying a message is very similar to signing except the EVP_DigestVerify* functions (or EVP_Verify* functions) are used instead. Clearly only a public key is required for a verify operation:
/* Initialize `key` with a public key */ if(1 != EVP_DigestVerifyInit(mdctx, NULL, EVP_sha256(), NULL, key)) goto err; /* Initialize `key` with a public key */ if(1 != EVP_DigestVerifyUpdate(mdctx, msg, strlen(msg))) goto err; if(1 == EVP_DigestVerifyFinal(mdctx, sig, slen)) { /* Success */ } else { /* Failure */ }
Note that MAC operations do not support the verify operation. Verifying a MAC code is done by calling the sign operations and confirming that the generated code is identical to the one provided. It is important that when comparing a supplied MAC with an expected MAC that the comparison takes a constant time whether the comparison returns a match or not. Failure to do this can expose your code to timing attacks, which could (for example) enable an attacker to forge MAC codes. To do this use the CRYPTO_memcmp function as shown in the code example below. Never use memcmp for this test:
if(!(mdctx = EVP_MD_CTX_create())) goto err; /* Create a buffer to store the MAC for the received message */ if(!(sigtmp = OPENSSL_malloc(sizeof(unsigned char) * EVP_PKEY_size(key)))) goto err; sigtmplen = EVP_PKEY_size(key); /* Calculate the MAC for the received message */ if(1 != EVP_DigestSignInit(mdctx, NULL, EVP_sha256(), NULL, key)) goto err; if(1 != EVP_DigestSignUpdate(mdctx, msg, strlen(msg))) goto err; if(1 != EVP_DigestSignFinal(mdctx, sigtmp, &sigtmplen)) goto err; /* Check the lengths of the calculated and supplied MACs are the same */ if(sigtmplen != slen) goto err; /* Calculated MAC is in sigtmp. Supplied MAC is in sig. Compare the two */ if(CRYPTO_memcmp(sig, sigtmp, slen)) /* Verify failure */ goto failure; else /* Verify success */;
Refer to Manual:EVP_DigestVerifyInit(3) and Manual:EVP_VerifyInit(3) for further information on the verify functions.
Downloads
t-hmac.c.tar.gz - sample program to sign and verify a string using an HMAC with the EVP_DigestSign* and EVP_DigestVerify* functions.
t-rsa.c.tar.gz - sample program to sign and verify a string using RSA with the EVP_DigestSign* and EVP_DigestVerify* functions.