Lines Matching refs:methods
250 B<EVP_PKEY_METHOD> is a structure which holds a set of methods for a
251 specific public key cryptographic algorithm. Those methods are usually
256 is a built-in static array representing the standard methods for different
258 methods, which can be manipulated by using L<EVP_PKEY_meth_add0(3)>.
265 The methods are the underlying implementations of a particular public key
281 The paramgen_init() and paramgen() methods deal with key parameter generation.
288 The keygen_init() and keygen() methods are used to generate the actual key for
296 The sign_init() and sign() methods are used to generate the signature of a
305 The verify_init() and verify() methods are used to verify whether a signature is
313 The verify_recover_init() and verify_recover() methods are used to verify a
322 The signctx_init() and signctx() methods are used to sign a digest present by
330 The verifyctx_init() and verifyctx() methods are used to verify a signature
338 The encrypt_init() and encrypt() methods are used to encrypt a piece of data.
345 The decrypt_init() and decrypt() methods are used to decrypt a piece of data.
351 The derive_init() and derive() methods are used to derive the shared secret
358 The ctrl() and ctrl_str() methods are used to adjust algorithm-specific
367 The digestsign() and digestverify() methods are used to generate or verify
375 The check(), public_check() and param_check() methods are used to validate a
400 in corresponding EVP methods by the EVP framework. Thus the implementations of
401 these methods don't need to care about handling the case of returning output
419 EVP_PKEY_meth_add0() adds B<pmeth> to the user defined stack of methods.
