Lines Matching refs:as
13 * the function signatures for functions that are offered as function
79 All "functions" mentioned here are passed as function pointers between
95 L<OSSL_DISPATCH(3)> arrays are indexed by numbers that are provided as
96 macros in L<openssl-core_dispatch.h(7)>, as follows:
135 represented as I<keydata> in this manual.
141 interface that we document here can be passed as is to other provider
142 operations, such as OP_signature_sign_init() (see
172 classification. In other words, this particular selector bit works as
186 =for comment This should used by EVP functions such as
229 OSSL_FUNC_keymgmt_gen() and OSSL_FUNC_keymgmt_gen_cleanup() work together as a
241 chooses can be used as a template for the key object to be generated.
273 OSSL_FUNC_keymgmt_load() are mandatory, as well as OSSL_FUNC_keymgmt_free() and
276 present as well.
305 but only works as an advisory. If this function is not present, or
307 from the same provider, of the same name as the one used to fetch the
315 not meaningful such as B<OSSL_KEYMGMT_SELECT_DOMAIN_PARAMETERS> for
316 RSA keys the function should just return 1 as the selected subset
331 not meaningful such as B<OSSL_KEYMGMT_SELECT_DOMAIN_PARAMETERS> for
332 RSA keys the function should just return 1 as there is nothing to validate for
347 I<param_cb> with that array as well as the given I<cbarg>.
378 keymgmt algorithms are as follows:
397 in order to properly support various use cases such as CMS signing.
412 keys from this keymgmt, this parameter should get its name as value.
425 keys from this keymgmt, this parameter should get its name as value.
429 B<OSSL_PKEY_PARAM_MANDATORY_DIGEST> is responded to as well,
436 with the corresponding signature operation, but may be specified as an
