EVP_DIGESTINIT(3SSL)

๐Ÿ’… EVP_DIGESTINIT(3SSL) โ€” OpenSSL ๐Ÿ’…

Okay bestie, this is the OpenSSL manual page for the whole EVP digest routine friend group โ€” message digests, XOFs, contexts, params, all of it. Buckle up, it's giving โ€œcryptographic group chatโ€ and we're getting into every detail. ๐Ÿ’–

โœจ NAME โœจ

This page covers the full squad โ€” literally all of these are EVP digest routines:

EVP_MD_fetch, EVP_MD_up_ref, EVP_MD_free, EVP_MD_get_params,
EVP_MD_gettable_params, EVP_MD_CTX_new, EVP_MD_CTX_reset,
EVP_MD_CTX_free, EVP_MD_CTX_dup, EVP_MD_CTX_copy, EVP_MD_CTX_copy_ex,
EVP_MD_CTX_ctrl, EVP_MD_CTX_set_params, EVP_MD_CTX_get_params,
EVP_MD_CTX_settable_params, EVP_MD_CTX_gettable_params,
EVP_MD_CTX_set_flags, EVP_MD_CTX_clear_flags, EVP_MD_CTX_test_flags,
EVP_Q_digest, EVP_Digest, EVP_DigestInit_ex2, EVP_DigestInit_ex,
EVP_DigestInit, EVP_DigestUpdate, EVP_DigestFinal_ex,
EVP_DigestFinalXOF, EVP_DigestFinal, EVP_DigestSqueeze, EVP_MD_is_a,
EVP_MD_get0_name, EVP_MD_get0_description, EVP_MD_names_do_all,
EVP_MD_get0_provider, EVP_MD_get_type, EVP_MD_get_pkey_type,
EVP_MD_get_size, EVP_MD_get_block_size, EVP_MD_get_flags,
EVP_MD_CTX_get0_name, EVP_MD_CTX_md, EVP_MD_CTX_get0_md,
EVP_MD_CTX_get1_md, EVP_MD_CTX_get_type, EVP_MD_CTX_get_size_ex,
EVP_MD_CTX_get_block_size, EVP_MD_CTX_get0_md_data,
EVP_MD_CTX_update_fn, EVP_MD_CTX_set_update_fn, EVP_md_null,
EVP_get_digestbyname, EVP_get_digestbynid, EVP_get_digestbyobj,
EVP_MD_CTX_get_pkey_ctx, EVP_MD_CTX_set_pkey_ctx,
EVP_MD_do_all_provided, EVP_MD_type, EVP_MD_nid, EVP_MD_name,
EVP_MD_pkey_type, EVP_MD_size, EVP_MD_block_size, EVP_MD_flags,
EVP_MD_xof, EVP_MD_CTX_size, EVP_MD_CTX_get_size, EVP_MD_CTX_block_size,
EVP_MD_CTX_type, EVP_MD_CTX_pkey_ctx, EVP_MD_CTX_md_data - EVP digest
routines

๐Ÿฆ‹ SYNOPSIS ๐Ÿฆ‹

This is the exact lineup, no cap:

#include <openssl/evp.h>

EVP_MD *EVP_MD_fetch(OSSL_LIB_CTX *ctx, const char *algorithm,
                     const char *properties);
int EVP_MD_up_ref(EVP_MD *md);
void EVP_MD_free(EVP_MD *md);
int EVP_MD_get_params(const EVP_MD *digest, OSSL_PARAM params[]);
const OSSL_PARAM *EVP_MD_gettable_params(const EVP_MD *digest);
EVP_MD_CTX *EVP_MD_CTX_new(void);
int EVP_MD_CTX_reset(EVP_MD_CTX *ctx);
void EVP_MD_CTX_free(EVP_MD_CTX *ctx);
void EVP_MD_CTX_ctrl(EVP_MD_CTX *ctx, int cmd, int p1, void* p2);
int EVP_MD_CTX_get_params(EVP_MD_CTX *ctx, OSSL_PARAM params[]);
int EVP_MD_CTX_set_params(EVP_MD_CTX *ctx, const OSSL_PARAM params[]);
const OSSL_PARAM *EVP_MD_settable_ctx_params(const EVP_MD *md);
const OSSL_PARAM *EVP_MD_gettable_ctx_params(const EVP_MD *md);
const OSSL_PARAM *EVP_MD_CTX_settable_params(EVP_MD_CTX *ctx);
const OSSL_PARAM *EVP_MD_CTX_gettable_params(EVP_MD_CTX *ctx);
void EVP_MD_CTX_set_flags(EVP_MD_CTX *ctx, int flags);
void EVP_MD_CTX_clear_flags(EVP_MD_CTX *ctx, int flags);
int EVP_MD_CTX_test_flags(const EVP_MD_CTX *ctx, int flags);

int EVP_Q_digest(OSSL_LIB_CTX *libctx, const char *name, const char *propq,
                 const void *data, size_t datalen,
                 unsigned char *md, size_t *mdlen);
int EVP_Digest(const void *data, size_t count, unsigned char *md,
               unsigned int *size, const EVP_MD *type, ENGINE *impl);
int EVP_DigestInit_ex2(EVP_MD_CTX *ctx, const EVP_MD *type,
                       const OSSL_PARAM params[]);
int EVP_DigestInit_ex(EVP_MD_CTX *ctx, const EVP_MD *type, ENGINE *impl);
int EVP_DigestUpdate(EVP_MD_CTX *ctx, const void *d, size_t cnt);
int EVP_DigestFinal_ex(EVP_MD_CTX *ctx, unsigned char *md, unsigned int *s);
int EVP_DigestFinalXOF(EVP_MD_CTX *ctx, unsigned char *out, size_t outlen);
int EVP_DigestSqueeze(EVP_MD_CTX *ctx, unsigned char *out, size_t outlen);

EVP_MD_CTX *EVP_MD_CTX_dup(const EVP_MD_CTX *in);
int EVP_MD_CTX_copy_ex(EVP_MD_CTX *out, const EVP_MD_CTX *in);

int EVP_DigestInit(EVP_MD_CTX *ctx, const EVP_MD *type);
int EVP_DigestFinal(EVP_MD_CTX *ctx, unsigned char *md, unsigned int *s);

int EVP_MD_CTX_copy(EVP_MD_CTX *out, EVP_MD_CTX *in);

const char *EVP_MD_get0_name(const EVP_MD *md);
const char *EVP_MD_get0_description(const EVP_MD *md);
int EVP_MD_is_a(const EVP_MD *md, const char *name);
int EVP_MD_names_do_all(const EVP_MD *md,
                        void (*fn)(const char *name, void *data),
                        void *data);
const OSSL_PROVIDER *EVP_MD_get0_provider(const EVP_MD *md);
int EVP_MD_get_type(const EVP_MD *md);
int EVP_MD_get_pkey_type(const EVP_MD *md);
int EVP_MD_get_size(const EVP_MD *md);
int EVP_MD_get_block_size(const EVP_MD *md);
unsigned long EVP_MD_get_flags(const EVP_MD *md);
int EVP_MD_xof(const EVP_MD *md);

const EVP_MD *EVP_MD_CTX_get0_md(const EVP_MD_CTX *ctx);
EVP_MD *EVP_MD_CTX_get1_md(EVP_MD_CTX *ctx);
const char *EVP_MD_CTX_get0_name(const EVP_MD_CTX *ctx);
int EVP_MD_CTX_get_size_ex(const EVP_MD_CTX *ctx);
int EVP_MD_CTX_get_block_size(const EVP_MD_CTX *ctx);
int EVP_MD_CTX_get_type(const EVP_MD_CTX *ctx);
void *EVP_MD_CTX_get0_md_data(const EVP_MD_CTX *ctx);

const EVP_MD *EVP_md_null(void);

const EVP_MD *EVP_get_digestbyname(const char *name);
const EVP_MD *EVP_get_digestbynid(int type);
const EVP_MD *EVP_get_digestbyobj(const ASN1_OBJECT *o);

EVP_PKEY_CTX *EVP_MD_CTX_get_pkey_ctx(const EVP_MD_CTX *ctx);
void EVP_MD_CTX_set_pkey_ctx(EVP_MD_CTX *ctx, EVP_PKEY_CTX *pctx);

void EVP_MD_do_all_provided(OSSL_LIB_CTX *libctx,
                            void (*fn)(EVP_MD *mac, void *arg),
                            void *arg);

#define EVP_MD_type EVP_MD_get_type
#define EVP_MD_nid EVP_MD_get_type
#define EVP_MD_name EVP_MD_get0_name
#define EVP_MD_pkey_type EVP_MD_get_pkey_type
#define EVP_MD_size EVP_MD_get_size
#define EVP_MD_block_size EVP_MD_get_block_size
#define EVP_MD_flags EVP_MD_get_flags
#define EVP_MD_CTX_get_size EVP_MD_CTX_get_size_ex
#define EVP_MD_CTX_size EVP_MD_CTX_get_size_ex
#define EVP_MD_CTX_block_size EVP_MD_CTX_get_block_size
#define EVP_MD_CTX_type EVP_MD_CTX_get_type
#define EVP_MD_CTX_pkey_ctx EVP_MD_CTX_get_pkey_ctx
#define EVP_MD_CTX_md_data EVP_MD_CTX_get0_md_data

And heads up, these ones have been deprecated since OpenSSL 3.0, and can be hidden entirely by defining OPENSSL_API_COMPAT with a suitable version value โ€” see openssl_user_macros(7):

const EVP_MD *EVP_MD_CTX_md(const EVP_MD_CTX *ctx);

int (*EVP_MD_CTX_update_fn(EVP_MD_CTX *ctx))(EVP_MD_CTX *ctx,
                                             const void *data, size_t count);

void EVP_MD_CTX_set_update_fn(EVP_MD_CTX *ctx,
                              int (*update)(EVP_MD_CTX *ctx,
                                            const void *data, size_t count));

๐ŸŒˆ DESCRIPTION ๐ŸŒˆ

The EVP digest routines are your high-level interface to message digests and Extendable Output Functions (XOF). Think of them as the VIP entrance to hashing, but make it OpenSSL.

The EVP_MD type is a structure for digest method implementation. It's the blueprint, not the finished smoothie. ๐Ÿ“

Each Message digest algorithm (such as SHA256) produces a fixed size output length, which is returned when EVP_DigestFinal_ex() is called. Extendable Output Functions (XOF) such as SHAKE256 are the iconique ones with a variable sized output length outlen, and you can use either EVP_DigestFinalXOF() or EVP_DigestSqueeze() with them. You can also use EVP_DigestFinal_ex() for an XOF, but bestie, the "xoflen" must be set beforehand (see PARAMETERS below). And note: EVP_MD_get_size() and EVP_MD_CTX_get_size_ex() behave differently for an XOF. Different vibes, literally.


๐ŸŒŸ EVP_MD_fetch()

Fetches the digest implementation for the given algorithm from any provider offering it, within the criteria given by the properties. See ALGORITHM FETCHING in crypto(7) for further information.

The returned value must eventually be freed with EVP_MD_free().

Fetched EVP_MD structures are reference counted. Slay.

๐ŸŒŸ EVP_MD_up_ref()

Increments the reference count for an EVP_MD structure. That's it. That's the whole job. ๐Ÿ’…

๐ŸŒŸ EVP_MD_free()

Decrements the reference count for the fetched EVP_MD structure. If the reference count drops to 0, then the structure is freed. If the argument is NULL, nothing is done โ€” no drama, no crash.

๐ŸŒŸ EVP_MD_CTX_new()

Allocates and returns a digest context. Fresh context, main character energy. โœจ

๐ŸŒŸ EVP_MD_CTX_reset()

Resets the digest context ctx. You can use this to reuse an already existing context instead of making a whole new one. Reuse era.

๐ŸŒŸ EVP_MD_CTX_free()

Cleans up digest context ctx and frees up the space allocated to it. If the argument is NULL, nothing is done.

๐ŸŒŸ EVP_MD_CTX_ctrl()

This is a legacy method, okay? EVP_MD_CTX_set_params() and EVP_MD_CTX_get_params() are the mechanism that should be used to set and get parameters that are used by providers.

That said: it performs digest-specific control actions on context ctx. The control command is indicated in cmd, and any additional arguments are in p1 and p2. EVP_MD_CTX_ctrl() must be called after EVP_DigestInit_ex2(). Other restrictions may apply depending on the control type and digest implementation.

If this function happens to be used with a fetched EVP_MD, it will translate the controls that are known to OpenSSL into OSSL_PARAM(3) parameters with keys defined by OpenSSL and call EVP_MD_CTX_get_params() or EVP_MD_CTX_set_params() as is appropriate for each control command.

See CONTROLS below for more information, including what translations are being done.

๐ŸŒŸ EVP_MD_get_params()

Retrieves the requested list of params from an MD md. See PARAMETERS below for more info.

๐ŸŒŸ EVP_MD_CTX_get_params()

Retrieves the requested list of params from an MD context ctx. See PARAMETERS below.

๐ŸŒŸ EVP_MD_CTX_set_params()

Sets the list of params into an MD context ctx. See PARAMETERS below.

๐ŸŒŸ EVP_MD_gettable_params()

Get a constant OSSL_PARAM(3) array that describes the retrievable parameters that can be used with EVP_MD_get_params(). It's the โ€œwhat can I ask for?โ€ list.

๐ŸŒŸ EVP_MD_gettable_ctx_params(), EVP_MD_CTX_gettable_params()

Get a constant OSSL_PARAM(3) array that describes the retrievable parameters that can be used with EVP_MD_CTX_get_params().

EVP_MD_gettable_ctx_params() returns the parameters that can be retrieved from the algorithm, whereas EVP_MD_CTX_gettable_params() returns the parameters that can be retrieved in the context's current state. Two different vibes, same param tea. ๐Ÿซถ

๐ŸŒŸ EVP_MD_settable_ctx_params(), EVP_MD_CTX_settable_params()

Get a constant OSSL_PARAM(3) array that describes the settable parameters that can be used with EVP_MD_CTX_set_params().

EVP_MD_settable_ctx_params() returns the parameters that can be set from the algorithm, whereas EVP_MD_CTX_settable_params() returns the parameters that can be set in the context's current state. Algorithm-level vs current-state-level, iykyk.

๐ŸŒŸ EVP_MD_CTX_set_flags(), EVP_MD_CTX_clear_flags(), EVP_MD_CTX_test_flags()

Sets, clears and tests ctx flags. See FLAGS below for more information. The flags section is right there waiting, bestie. ๐Ÿ’œ

  • EVP_Q_digest() โ€” the quick lil one-shot digest bestie โœจ. It hashes datalen bytes of data at data using the digest algorithm name, which gets fetched using the optional libctx and propq parameters. Digest value goes in md, and its length is written at mdlen if that pointer isn't NULL. At most EVP_MAX_MD_SIZE bytes get written, no cap.
  • EVP_Digest() โ€” basically a wrapper around the Digest Init_ex, Update and Final_ex functions ๐Ÿซถ. Hashes count bytes of data at data using a digest type from the ENGINE impl. Digest value lands in md and its length is written at size if that pointer isn't NULL. At most EVP_MAX_MD_SIZE bytes will be written. If impl is NULL, the default implementation of the digest type is used โ€” iconic default behaviour ๐Ÿ’….
  • EVP_DigestInit_ex2() โ€” sets up digest context ctx to use a digest type ๐ŸŽ€. type is typically supplied by something like EVP_sha1(), or a value explicitly fetched with EVP_MD_fetch(). ctx MUST NOT be NULL โ€” like, do not do that, fr fr.

The parameters params are set on the context after initialisation, cute.

type can be NULL if ctx has already been initialized with another EVP_DigestInit_ex() call and has not been reset with EVP_MD_CTX_reset().

  • EVP_DigestInit_ex() โ€” same vibe, sets up digest context ctx to use a digest type. type is typically supplied by a function such as EVP_sha1(), or a value explicitly fetched with EVP_MD_fetch().

If impl is non-NULL, its implementation of the digest type is used if there is one, and if there isn't, the default implementation steps in ๐Ÿ™ˆ.

Again: type can be NULL if ctx has already been initialized with another EVP_DigestInit_ex() call and has not been reset with EVP_MD_CTX_reset().

  • EVP_DigestUpdate() โ€” hashes cnt bytes of data at d into the digest context ctx ๐Ÿ”ฅ. You can call this several times on the same ctx to hash additional data โ€” stack that data, bestie.
  • EVP_DigestFinal_ex() โ€” retrieves the digest value from ctx and places it in md ๐ŸŒธ. If the s parameter isn't NULL, the number of bytes of data written (i.e. the length of the digest) gets written to the integer at s. At most EVP_MAX_MD_SIZE bytes will be written โ€” unless the digest implementation allows changing the digest size and it's been set to a larger value by the application ๐Ÿ‘€.
After calling EVP_DigestFinal_ex() you cannot make any more EVP_DigestUpdate() calls on that context. You can call EVP_DigestInit_ex2() to initialize a new digest operation though. And ctx MUST NOT be NULL โ€” periodt.
  • EVP_DigestFinalXOF() โ€” the interface to extendable-output functions, XOFs, like SHAKE128 and SHAKE256 ๐Ÿฆ‹. It retrieves the digest value from ctx and places it in the outlen-sized out.
After calling this, no more EVP_DigestUpdate() calls โ€” but EVP_DigestInit_ex2() can spin up a new operation. Also EVP_DigestFinalXOF() may only be called once, so make it count ๐Ÿ’….
  • EVP_DigestSqueeze() โ€” similar to EVP_DigestFinalXOF() but it lets you make multiple calls to squeeze out variable length output data ๐Ÿ“. And heads up: EVP_DigestFinalXOF() should not be called after this.
  • EVP_MD_CTX_dup() โ€” duplicates the message digest state from in โœจ. So useful for avoiding multiple EVP_MD_fetch() calls, or when you've got large amounts of data to hash that only differ in the last few bytes. Work smarter, not harder.
  • EVP_MD_CTX_copy_ex() โ€” copies the message digest state from in to out ๐ŸŽ€. Same reasoning: it's a lifesaver if large amounts of data are to be hashed which only differ in the last few bytes.
  • EVP_DigestInit() โ€” behaves in the same way as EVP_DigestInit_ex2() except it doesn't set any parameters and it calls EVP_MD_CTX_reset(), so it literally cannot be used with a type of NULL ๐Ÿ˜ญ.
  • EVP_DigestFinal() โ€” similar to EVP_DigestFinal_ex() except after computing the digest, the digest context ctx is automatically cleaned up with EVP_MD_CTX_reset() ๐Ÿงš. Self-cleaning, we love her.
  • EVP_MD_CTX_copy() โ€” similar to EVP_MD_CTX_copy_ex() except the destination out does not have to be initialized ๐Ÿ’–.
  • EVP_MD_is_a() โ€” returns 1 if md is an implementation of an algorithm that's identifiable with name, otherwise 0 โœ….

If md is a legacy digest (like, it's the return value from the likes of EVP_sha256() rather than the result of an EVP_MD_fetch()), only cipher names registered with the default library context (see OSSL_LIB_CTX(3)) will be considered ๐Ÿ‘‘

  • EVP_MD_xof() โ€” returns 1 if md is an Extendable-output Function (XOF), otherwise 0 ๐ŸŒˆ. SHAKE128 and SHAKE256 are XOF functions. It returns 0 for BLAKE2B algorithms, just so you know.
  • EVP_MD_get0_name(), EVP_MD_CTX_get0_name() โ€” return the name of the given message digest ๐Ÿท๏ธ. For fetched message digests with multiple names, only one of them gets returned; it's recommended to use EVP_MD_names_do_all() instead, iykyk.
  • EVP_MD_names_do_all() โ€” traverses all names for the md, and calls fn with each name and data ๐ŸŒŸ. This is only useful with fetched EVP_MDs.
  • EVP_MD_get0_description() โ€” returns a description of the digest, meant for display and human consumption ๐Ÿ’œ. The description is at the discretion of the digest implementation, so it's giving "each algorithm writes its own bio".
  • EVP_MD_get0_provider() โ€” returns an OSSL_PROVIDER pointer to the provider that implements the given EVP_MD ๐Ÿ”Œ.
  • EVP_MD_get_size() โ€” returns the size of the message digest when passed an EVP_MD, i.e. the size of the hash ๐Ÿ“. A negative value or 0 can occur for invalid size. For an XOF with no default size, this returns 0.
  • EVP_MD_CTX_get_size_ex(), EVP_MD_CTX_get_size() โ€” for a normal digest this is the same as EVP_MD_get_size() ๐Ÿซถ. For an XOF it returns the "xoflen" if it's been set, otherwise it returns 0.
  • EVP_MD_get_block_size(), EVP_MD_CTX_get_block_size() โ€” return the block size of the message digest when passed an EVP_MD or an EVP_MD_CTX structure ๐Ÿงฑ.
  • EVP_MD_get_type(), EVP_MD_CTX_get_type() โ€” return the NID of the OBJECT IDENTIFIER representing the given message digest when passed an EVP_MD structure ๐ŸŒธ. Like, for example:
EVP_MD_get_type(EVP_sha1())

returns NID_sha1. This function is normally used when setting ASN1 OIDs, bestie ๐Ÿ’….

  • EVP_MD_CTX_get0_md_data() โ€” returns the digest method private data for the passed EVP_MD_CTX ๐Ÿ”. The space is allocated by OpenSSL and has the size originally set with EVP_MD_meth_set_app_datasize().
  • EVP_MD_CTX_get0_md(), EVP_MD_CTX_get1_md() โ€” EVP_MD_CTX_get0_md() returns the EVP_MD structure corresponding to the passed EVP_MD_CTX ๐Ÿ’–. This will be the same EVP_MD object originally passed to EVP_DigestInit_ex2() (or other similar function) when the EVP_MD_CTX was first initialised.
Careful though: where explicit fetch is in use (see EVP_MD_fetch(3)), the value returned from this function will not have its reference count incremented, so it should not be used after the EVP_MD_CTX is freed ๐Ÿ’€.

EVP_MD_CTX_get1_md() is the same except the ownership is passed to the caller and is from the passed EVP_MD_CTX.

  • EVP_MD_CTX_set_update_fn() โ€” sets the update function for ctx to update ๐Ÿ”ง. This is the function that's called by EVP_DigestUpdate(). If it's not set, the update function from the EVP_MD type specified at initialization is used.
  • EVP_MD_CTX_update_fn() โ€” returns the update function for ctx ๐ŸŽฏ.
  • EVP_MD_get_flags() โ€” returns the md flags ๐Ÿšฉ. Note that these are different from the EVP_MD_CTX ones. See EVP_MD_meth_set_flags(3) for more information.
  • EVP_MD_get_pkey_type() โ€” returns the NID of the public key signing algorithm associated with this digest ๐Ÿ”‘. For example EVP_sha1() is associated with RSA so this will return NID_sha1WithRSAEncryption. Since digests and signature algorithms are no longer linked, this function is only retained for compatibility reasons โ€” it's legacy energy, but we respect it.
  • EVP_md_null() โ€” a "null" message digest that does literally nothing: i.e. the hash it returns is of zero length ๐Ÿ’€ (the original main-character-of-nothing).
  • EVP_get_digestbyname(), EVP_get_digestbynid(), EVP_get_digestbyobj() โ€” return an EVP_MD structure when passed a digest name, a digest NID or an ASN1_OBJECT structure respectively ๐ŸŽ€.

The EVP_get_digestbyname() function is present for backwards compatibility with OpenSSL prior to version 3 and is different to the EVP_MD_fetch() function since it does not attempt to "fetch" an implementation of the cipher. Additionally, it only knows about digests that are built-in to OpenSSL and have an associated NID. Similarly EVP_get_digestbynid() and EVP_get_digestbyobj() also return objects without an associated implementation ๐Ÿ‘€.

When the digest objects returned by these functions are used (such as in a call to EVP_DigestInit_ex()), an implementation of the digest will be implicitly fetched from the loaded providers. This fetch could fail if no suitable implementation is available ๐Ÿ˜ญ. Use EVP_MD_fetch() instead to explicitly fetch the algorithm and an associated implementation from a provider.

See "ALGORITHM FETCHING" in crypto(7) for more information about fetching.

The digest objects returned from these functions do not need to be freed with EVP_MD_free() โ€” good news honestly.

  • EVP_MD_CTX_get_pkey_ctx() โ€” returns the EVP_PKEY_CTX assigned to ctx ๐Ÿ”. The returned pointer should not be freed by the caller.
  • EVP_MD_CTX_set_pkey_ctx() โ€” assigns an EVP_PKEY_CTX to EVP_MD_CTX ๐Ÿ’…. This is usually used to provide a customized EVP_PKEY_CTX to EVP_DigestSignInit(3) or EVP_DigestVerifyInit(3). The pctx passed to this function should be freed by the caller. A NULL pctx pointer is also allowed, to clear the EVP_PKEY_CTX assigned to ctx. In that case, whether the cleared EVP_PKEY_CTX gets freed or not depends on how the EVP_PKEY_CTX is created ๐ŸŒ€.
  • EVP_MD_do_all_provided() โ€” traverses all message digests implemented by all activated providers in the given library context libctx, and for each of the implementations, calls the given function fn with the implementation method and the given arg as argument ๐ŸŒˆ๐Ÿ‘‘.

๐ŸŽ›๏ธ PARAMETERS

Okay bestie, before we get into the actual keys โ€” peep OSSL_PARAM(3) for the whole tea on passing parameters, that's your homework. ๐Ÿ“š

So EVP_MD_CTX_set_params() and EVP_MD_CTX_get_params() both play nice with these OSSL_PARAM keys:

  • "xoflen" (OSSL_DIGEST_PARAM_XOFLEN) <unsigned integer> โ€” sets or gets the digest length for extendable output functions. The value should not exceed what can be given using a size_t (don't be messy about it ๐Ÿ’…). SHAKE-128 and SHAKE-256 may use it to set the output length that EVP_DigestFinal_ex() and EVP_DigestFinal() use.
  • "size" (OSSL_DIGEST_PARAM_SIZE) <unsigned integer> โ€” sets or gets a fixed digest length. Again: the value should not exceed what can be given using a size_t. BLAKE2B-512 may use it to set the output length used by EVP_DigestFinal_ex() and EVP_DigestFinal().

EVP_MD_CTX_set_params() gets its own exclusive little list โ€” these keys are set-only:

  • "pad-type" (OSSL_DIGEST_PARAM_PAD_TYPE) <unsigned integer> โ€” sets the padding type. The MDC2 algorithm is the one using this. ๐Ÿงฉ

And EVP_MD_CTX_get_params() has its own get-only key too:

  • "micalg" (OSSL_DIGEST_PARAM_MICALG) <UTF8 string> โ€” gets the digest Message Integrity Check algorithm string. This is the one used when you're creating S/MIME multipart/signed messages, exactly as specified in RFC 3851. External engines or providers may use it. โœจ

๐ŸŽฎ CONTROLS

EVP_MD_CTX_ctrl() is your remote control โ€” it can send these standard controls:

  • EVP_MD_CTRL_MICALG โ€” gets the digest Message Integrity Check algorithm string. Yep, same S/MIME multipart/signed situation, as specified in RFC 3851. The string value gets written to p2. When you use this with a fetched EVP_MD, EVP_MD_CTX_get_params() gets called with an OSSL_PARAM(3) item with the key "micalg" (OSSL_DIGEST_PARAM_MICALG).
  • EVP_MD_CTRL_XOF_LEN โ€” this control sets the digest length for extendable output functions to p1. Sending this control directly should not be necessary, bestie โ€” using EVP_DigestFinalXOF() is the preferred glow-up route. Currently used by SHAKE algorithms. When you use this with a fetched EVP_MD, EVP_MD_CTX_get_params() gets called with an OSSL_PARAM(3) item with the key "xoflen" (OSSL_DIGEST_PARAM_XOFLEN).

๐Ÿšฉ FLAGS

EVP_MD_CTX_set_flags(), EVP_MD_CTX_clear_flags() and EVP_MD_CTX_test_flags() are the trio you use to manipulate and test these EVP_MD_CTX flags:

  • EVP_MD_CTX_FLAG_ONESHOT โ€” tells the digest to optimize for one update only, if possible. Main-character efficiency. โšก
  • EVP_MD_CTX_FLAG_CLEANED โ€” internal use only. Must not be used in user code. Hands off. ๐Ÿ™…
  • EVP_MD_CTX_FLAG_REUSE โ€” also internal use only, also must not be used in user code. Same energy. ๐Ÿ™…
  • EVP_MD_CTX_FLAG_NO_INIT โ€” instructs EVP_DigestInit() and similar functions not to initialise the implementation specific data.
  • EVP_MD_CTX_FLAG_FINALISE โ€” some functions like EVP_DigestSign only finalise copies of internal contexts, so that additional data can be included after the finalisation call. That's inefficient if you don't actually need the functionality, and this flag disables it. ๐Ÿช„

๐Ÿ” RETURN VALUES

Okay, here's the receipts โ€” what every single one of these gives you back:

  • EVP_MD_fetch() โ€” returns a pointer to a EVP_MD for success, or NULL for failure.
  • EVP_MD_up_ref() โ€” returns 1 for success or 0 for failure.
  • EVP_Q_digest(), EVP_Digest(), EVP_DigestInit_ex2(), EVP_DigestInit_ex(), EVP_DigestInit(), EVP_DigestUpdate(), EVP_DigestFinal_ex(), EVP_DigestFinalXOF(), and EVP_DigestFinal() โ€” return 1 for success and 0 for failure.
  • EVP_MD_CTX_ctrl() โ€” returns 1 if successful or 0 for failure.
  • EVP_MD_CTX_set_params(), EVP_MD_CTX_get_params() โ€” returns 1 if successful or 0 for failure.
  • EVP_MD_CTX_settable_params(), EVP_MD_CTX_gettable_params() โ€” return an array of constant OSSL_PARAM(3)s, or NULL if there is none to get.
  • EVP_MD_CTX_dup() โ€” returns a new EVP_MD_CTX if successful or NULL on failure.
  • EVP_MD_CTX_copy_ex() โ€” returns 1 if successful or 0 for failure.
  • EVP_MD_get_type(), EVP_MD_get_pkey_type() โ€” returns the NID of the corresponding OBJECT IDENTIFIER, or NID_undef if none exists.
  • EVP_MD_get_size(), EVP_MD_get_block_size(), EVP_MD_CTX_get_size(), EVP_MD_CTX_get_block_size() โ€” returns the digest or block size in bytes, or -1 for failure.
  • EVP_md_null() โ€” returns a pointer to the EVP_MD structure of the "null" message digest.
  • EVP_get_digestbyname(), EVP_get_digestbynid(), EVP_get_digestbyobj() โ€” returns either an EVP_MD structure or NULL if an error occurs.
  • EVP_MD_CTX_set_pkey_ctx() โ€” this function has no return value. Nothing. Nada. ๐Ÿ’€
  • EVP_MD_names_do_all() โ€” returns 1 if the callback was called for all names. A return value of 0 means that the callback was not called for any names.

๐Ÿ“ NOTES

The EVP interface to message digests should almost always be used in preference to the low-level interfaces. Why? Because then your code becomes transparent to the digest being used and so much more flexible. It's giving adaptable. ๐Ÿฆ‹

New applications should use the SHA-2 (such as EVP_sha256(3)) or the SHA-3 digest algorithms (such as EVP_sha3_512(3)). The other digest algorithms are still in common use, so no shade to them, but yeah. ๐Ÿ‘‘

For most applications the impl parameter to EVP_DigestInit_ex() will be set to NULL to use the default digest implementation.

โš ๏ธ Lowkey important, bestie: ignoring failure returns of EVP_DigestInit_ex(), EVP_DigestInit_ex2(), or EVP_DigestInit() can lead to undefined behavior on subsequent calls updating or finalizing the EVP_MD_CTX, such as the EVP_DigestUpdate() or EVP_DigestFinal() functions. The only valid calls on the EVP_MD_CTX when initialization fails are calls that attempt another initialization of the context or release the context. That's it. Periodt. ๐Ÿ›‘

The functions EVP_DigestInit(), EVP_DigestFinal() and EVP_MD_CTX_copy() are obsolete but are retained to maintain compatibility with existing code. New applications should use EVP_DigestInit_ex(), EVP_DigestFinal_ex() and EVP_MD_CTX_copy_ex() instead โ€” because they can efficiently reuse a digest context instead of initializing and cleaning it up on each call, and they allow non default implementations of digests to be specified. Reuse era. โ™ป๏ธ

If digest contexts are not cleaned up after use, memory leaks will occur. ๐Ÿ˜ญ Not the vibe. Clean up your contexts.

EVP_MD_CTX_get0_name(), EVP_MD_CTX_get_size(), EVP_MD_CTX_get_block_size(), EVP_MD_CTX_get_type(), EVP_get_digestbynid() and EVP_get_digestbyobj() are defined as macros. iykyk.

EVP_MD_CTX_ctrl() sends commands to message digests for additional configuration or control.


๐Ÿ’ป EXAMPLES

This example digests the data "Test Message\n" and "Hello World\n", using the digest name passed on the command line. She's simple, she's iconic:

#include <stdio.h>
#include <string.h>
#include <openssl/evp.h>

int main(int argc, char *argv[])
{
    EVP_MD_CTX *mdctx;
    const EVP_MD *md;
    char mess1[] = "Test Message\n";
    char mess2[] = "Hello World\n";
    unsigned char md_value[EVP_MAX_MD_SIZE];
    unsigned int md_len, i;

    if (argv[1] == NULL) {
        printf("Usage: mdtest digestname\n");
        exit(1);
    }

    md = EVP_get_digestbyname(argv[1]);
    if (md == NULL) {
        printf("Unknown message digest %s\n", argv[1]);
        exit(1);
    }

    mdctx = EVP_MD_CTX_new();
    if (mdctx == NULL) {
       printf("Message digest create failed.\n");
       exit(1);
    }
    if (!EVP_DigestInit_ex2(mdctx, md, NULL)) {
        printf("Message digest initialization failed.\n");
        EVP_MD_CTX_free(mdctx);
        exit(1);
    }
    if (!EVP_DigestUpdate(mdctx, mess1, strlen(mess1))) {
        printf("Message digest update failed.\n");
        EVP_MD_CTX_free(mdctx);
        exit(1);
    }
    if (!EVP_DigestUpdate(mdctx, mess2, strlen(mess2))) {
        printf("Message digest update failed.\n");
        EVP_MD_CTX_free(mdctx);
        exit(1);
    }
    if (!EVP_DigestFinal_ex(mdctx, md_value, &md_len)) {
        printf("Message digest finalization failed.\n");
        EVP_MD_CTX_free(mdctx);
        exit(1);
    }
    EVP_MD_CTX_free(mdctx);

    printf("Digest is: ");
    for (i = 0; i < md_len; i++)
        printf("%02x", md_value[i]);
    printf("\n");

    exit(0);
}

๐Ÿ‘€ SEE ALSO

The whole friend group: EVP_MD_meth_new(3), openssl-dgst(1), evp(7), OSSL_PROVIDER(3), OSSL_PARAM(3), property(7), "ALGORITHM FETCHING" in crypto(7), provider-digest(7), life_cycle-digest(7) ๐Ÿซถ

The full list of digest algorithms are provided below, bestie โ€” go wild:

EVP_blake2b512(3), EVP_md2(3), EVP_md4(3), EVP_md5(3), EVP_mdc2(3), EVP_ripemd160(3), EVP_sha1(3), EVP_sha224(3), EVP_sha3_224(3), EVP_sm3(3), EVP_whirlpool(3)


๐Ÿ•ฐ๏ธ HISTORY

Let's take a lil stroll down memory lane, shall we? ๐ŸŒธ

The EVP_MD_CTX_create() and EVP_MD_CTX_destroy() functions were renamed to EVP_MD_CTX_new() and EVP_MD_CTX_free() in OpenSSL 1.1.0, respectively.

The link between digests and signing algorithms was fixed in OpenSSL 1.0 and later, so now EVP_sha1() can be used with RSA and DSA. Slay. ๐Ÿ’…

The EVP_dss1() function was removed in OpenSSL 1.1.0. Gone but not forgotten. ๐Ÿ•Š๏ธ

The EVP_MD_CTX_set_pkey_ctx() function was added in OpenSSL 1.1.1.

The EVP_Q_digest(), EVP_DigestInit_ex2(), EVP_MD_fetch(), EVP_MD_free(), EVP_MD_up_ref(), EVP_MD_get_params(), EVP_MD_CTX_set_params(), EVP_MD_CTX_get_params(), EVP_MD_gettable_params(), EVP_MD_gettable_ctx_params(), EVP_MD_settable_ctx_params(), EVP_MD_CTX_settable_params() and EVP_MD_CTX_gettable_params() functions were added in OpenSSL 3.0.

The EVP_MD_type(), EVP_MD_nid(), EVP_MD_name(), EVP_MD_pkey_type(), EVP_MD_size(), EVP_MD_block_size(), EVP_MD_flags(), EVP_MD_CTX_size(), EVP_MD_CTX_block_size(), EVP_MD_CTX_type(), and EVP_MD_CTX_md_data() functions were renamed to include "get" or "get0" in their names in OpenSSL 3.0, respectively. The old names are kept as non-deprecated alias macros, so nobody's code gets left behind. ๐Ÿซถ

The EVP_MD_CTX_md() function was deprecated in OpenSSL 3.0; use EVP_MD_CTX_get0_md() instead. EVP_MD_CTX_update_fn() and EVP_MD_CTX_set_update_fn() were deprecated in OpenSSL 3.0.

The EVP_MD_CTX_dup() function was added in OpenSSL 3.1.

The EVP_DigestSqueeze() function was added in OpenSSL 3.3.

The EVP_MD_CTX_get_size_ex() and EVP_xof() functions were added in OpenSSL 3.4. The macros EVP_MD_CTX_get_size() and EVP_MD_CTX_size were changed in OpenSSL 3.4 to be aliases for EVP_MD_CTX_get_size_ex(), previously they were aliases for EVP_MD_get_size which returned a constant value. This is required for XOF digests since they do not have a fixed size. ๐ŸŒ€

okay bestie, legal era incoming, but it's actually short so stay with me ๐Ÿซถ

Copyright 2000-2024 The OpenSSL Project Authors. All Rights Reserved. like, every last one of them, no cap ๐Ÿ‘‘

This file is licensed under the Apache License 2.0 (the "License"). The way that's phrased: you may not use this file except in compliance with the License โ€” so like, read it first, it's giving "terms and conditions but make it actually matter" ๐Ÿ˜ญ

You can grab a copy of the License in the file LICENSE in the source distribution, or at:

https://www.openssl.org/source/license.html

that's the whole thing. licensing lore, delivered ๐Ÿ’…


and that's a wrap on EVP_DIGESTINIT(3SSL), bestie!! ๐ŸŽ€ this iconic little page is from OpenSSL sources, version 3.5.7, dated 2026-06-09 โœจ go forth and digest responsibly, mwah ๐Ÿ’œ๐Ÿฆ‹๐ŸŒธ

๐Ÿ“ฆ where this page comes from