EVP_PKEY_DECRYPT(3)

πŸ“¦ version 4.4.0, in alpine 3.24, arch rolling

Okay so bestie, welcome to EVP_PKEY_DECRYPT(3) from the Library Functions Manual πŸ’…βœ¨ β€” this is the whole page, but make it make sense. It's giving public-key decryption setup, buffer-length moments, and one extremely important -2. No cap.

🌸 NAME 🌸

EVP_PKEY_decrypt_init, EVP_PKEY_decrypt β€” decrypt using a public key algorithm.


✨ SYNOPSIS ✨

First things first: it wants the library β€œlibcrypto” and this exact include, okay?

library β€œlibcrypto” #include <openssl/evp.h>

int
EVP_PKEY_decrypt_init(EVP_PKEY_CTX *ctx);

int
EVP_PKEY_decrypt(EVP_PKEY_CTX *ctx, unsigned char *out, size_t *outlen,
    const unsigned char *in, size_t inlen);

πŸ¦‹ DESCRIPTION πŸ¦‹

Here's the tea, bestie:

  • EVP_PKEY_decrypt_init() β€” initializes a public key algorithm context using key ctx->pkey for a decryption operation. Setup era, fr fr.
  • EVP_PKEY_decrypt() β€” performs a public key decryption operation using ctx. The data to be decrypted is specified using the in and inlen parameters. If out is NULL then the maximum size of the output buffer is written to the outlen parameter. If out is not NULL then before the call the outlen parameter should contain the length of the out buffer. If the call is successful, the decrypted data is written to out and the amount of data written to outlen. Buffer math, but make it fashion πŸ’….

After the call to EVP_PKEY_decrypt_init(), algorithm specific control operations can be performed to set any appropriate parameters for the operation. That's your little customisation window, iykyk.

The function EVP_PKEY_decrypt() can be called more than once on the same context if several operations are performed using the same parameters. Reuse is iconic, periodt.


🫢 RETURN VALUES 🫢

EVP_PKEY_decrypt_init() and EVP_PKEY_decrypt() return 1 for success and 0 or a negative value for failure. In particular, a return value of -2 indicates the operation is not supported by the public key algorithm.

So 1 is slay, 0 or negative is not the vibe, and -2 is literally the algorithm saying β€œnot supported” πŸ’€.


πŸ”₯ EXAMPLES πŸ”₯

Decrypt data using OAEP (for RSA keys):

Obsessed with a full example? Same. Here it is, exactly:

#include <openssl/evp.h>
#include <openssl/rsa.h>

EVP_PKEY_CTX *ctx;
unsigned char *out, *in;
size_t outlen, inlen;
EVP_PKEY *key;

/*
 * Assumes that key, in, and inlen are already set up
 * and that key is an RSA private key.
 */
ctx = EVP_PKEY_CTX_new(key, NULL);
if (!ctx)
        /* Error occurred */
if (EVP_PKEY_decrypt_init(ctx) <= 0)
        /* Error */
if (EVP_PKEY_CTX_set_rsa_padding(ctx, RSA_PKCS1_OAEP_PADDING) <= 0)
        /* Error */

/* Determine buffer length */
if (EVP_PKEY_decrypt(ctx, NULL, &outlen, in, inlen) <= 0)
        /* Error */

out = malloc(outlen);

if (!out)
        /* malloc failure */

if (EVP_PKEY_decrypt(ctx, out, &outlen, in, inlen) <= 0)
        /* Error */

/* Decrypted data is outlen bytes written to buffer out */

🌈 SEE ALSO 🌈

Go see also: EVP_PKEY_CTX_new(3), EVP_PKEY_derive(3), EVP_PKEY_encrypt(3), EVP_PKEY_sign(3), EVP_PKEY_verify(3), EVP_PKEY_verify_recover(3).


πŸŽ€ HISTORY πŸŽ€

History lesson, bestie: EVP_PKEY_decrypt_init() and EVP_PKEY_decrypt() first appeared in OpenSSL 1.0.0 and have been available since OpenBSD 4.9.


xoxo, Debian πŸ’– β€” June 8, 2025 β€” EVP_PKEY_DECRYPT(3) signing off! πŸŽ€

πŸ“¦ where this page comes from