Searched refs:dispatch (Results 1 – 18 of 18) sorted by relevance
| /openssl-master/test/ |
| A D | filterprov.c | 31 } dispatch[MAX_FILTERS]; member
87 if (globs->dispatch[i].operation == operation_id) { in filter_query()
89 return globs->dispatch[i].alg; in filter_query()
109 if (globs->dispatch[i].alg == algs) in filter_unquery()
209 globs->dispatch[globs->num_dispatch].alg[algnum++] = *algs; in filter_provider_set_filter()
218 globs->dispatch[globs->num_dispatch].operation = operation; in filter_provider_set_filter()
|
| /openssl-master/doc/man7/ |
| A D | openssl-core_dispatch.h.pod | 6 - OpenSSL provider dispatch numbers and function types
15 numbers, dispatch numbers and provider interface function types
18 The operation and dispatch numbers are represented with macros, which
35 With every dispatch number, there is an associated function type.
|
| A D | provider.pod | 55 dispatch array I<in>.
57 I<in> is a dispatch array of base functions offered by the OpenSSL
61 I<*out> must be assigned a dispatch array of base functions that the
|
| A D | ssl.pod | 46 This is a dispatch structure describing the internal B<ssl> library
|
| A D | openssl-core.h.pod | 53 definition (string) and a dispatch table (array of B<OSSL_DISPATCH>).
|
| A D | provider-rand.pod | 85 The parameter I<parent_calls> points to the dispatch table for I<parent>.
|
| A D | provider-base.pod | 41 * dispatch
364 provider_get0_dispatch() gets the dispatch table registered by the provider
|
| /openssl-master/providers/implementations/rands/ |
| A D | drbg.c | 41 static const OSSL_DISPATCH *find_call(const OSSL_DISPATCH *dispatch,
726 static const OSSL_DISPATCH *find_call(const OSSL_DISPATCH *dispatch, in find_call() argument
729 if (dispatch != NULL) in find_call()
730 while (dispatch->function_id != 0) { in find_call()
731 if (dispatch->function_id == function) in find_call()
732 return dispatch; in find_call()
733 dispatch++; in find_call()
|
| /openssl-master/doc/internal/man3/ |
| A D | ossl_method_construct.pod | 36 on provider dispatch tables need to do so in exactly the same way.
55 providers for a dispatch table given an I<operation_id>, and then
81 when the provider doesn't want its dispatch table stored in a longer
123 dispatch table I<fns>.
|
| A D | evp_generic_fetch.pod | 70 dispatch table I<fns>, with name identity I<name_id>.
|
| A D | ossl_provider_new.pod | 241 ossl_provider_get0_dispatch() returns the dispatch table that the provider
|
| /openssl-master/crypto/evp/ |
| A D | evp_rand.c | 32 const OSSL_DISPATCH *dispatch; member
136 rand->dispatch = fns; in evp_rand_from_algorithm()
355 parent_dispatch = parent->meth->dispatch; in EVP_RAND_CTX_new()
|
| /openssl-master/doc/man3/ |
| A D | ASYNC_WAIT_CTX_new.pod | 173 code would initiate cryptographic operations, and the engine code would dispatch
174 this operation to hardware, and if the dispatch is successful, then the engine
|
| A D | OSSL_LIB_CTX.pod | 42 useful for provider authors. The I<handle> and dispatch structure arguments
|
| A D | OSSL_PROVIDER.pod | 140 OSSL_PROVIDER_get0_dispatch() returns the provider's dispatch table as it was
|
| /openssl-master/crypto/ |
| A D | provider_core.c | 191 const OSSL_DISPATCH *dispatch; member
911 prov->dispatch = provider_dispatch; in provider_init()
1448 return prov->dispatch; in ossl_provider_get0_dispatch()
|
| /openssl-master/ |
| A D | INSTALL.md | 1774 the idea of performing dispatch at run-time, which is facilitated by the special
|
| A D | CHANGES.md | 10894 * Optionally dispatch EC_POINT_mul(), EC_POINT_precompute_mult()
|
Completed in 40 milliseconds