Lines Matching refs:context
79 To make things less ambiguous, this manual talks about a "context" or
80 "MAC context", which is to denote the MAC level context, and about a
81 "underlying context", or "computation context", which is to denote the
82 context for the underlying computation algorithm if there is one.
88 B<EVP_MAC_CTX> is a context type that holds internal MAC information
89 as well as a reference to a computation context, for those MACs that
95 a library context I<libctx> and a set of I<properties>.
112 EVP_MAC_CTX_new() creates a new context for the MAC type I<mac>.
113 The created context can then be used with most other functions
116 EVP_MAC_CTX_free() frees the contents of the context, including an
117 underlying context if there is one, as well as the context itself.
120 EVP_MAC_CTX_dup() duplicates the I<src> context and returns a newly allocated
121 context.
123 EVP_MAC_CTX_get0_mac() returns the B<EVP_MAC> associated with the context
141 EVP_MAC_init() sets up the underlying context I<ctx> with information given
173 Note that a parameter that is unknown in the underlying context is
177 context I<ctx> and its underlying context.
180 Note that a parameter that is unknown in the underlying context is
184 context, given a context I<ctx>.
187 If I<params> are NULL, the underlying context should do nothing and return 1.
188 Note that a parameter that is unknown in the underlying context is
202 the parameters that can be retrieved in the context's current state.
209 be retrieved in the context's current state.
213 EVP_MAC_CTX_get_mac_size() returns the MAC output size for the given context.
215 EVP_MAC_CTX_get_block_size() returns the MAC block size for the given context.
225 providers in the given library context I<libctx>, and for each of the
352 underlying CIPHER context, and so calling EVP_MAC_init() on an EVP_MAC object
