Latest update.
This commit is contained in:
@@ -47,9 +47,9 @@ for further information.
|
||||
|
||||
The asymmetric cipher (OSSL_OP_ASYM_CIPHER) operation enables providers to
|
||||
implement asymmetric cipher algorithms and make them available to applications
|
||||
via the API functions L<EVP_PKEY_encrypt_init_ex(3)>, L<EVP_PKEY_encrypt(3)>,
|
||||
L<EVP_PKEY_decrypt_init_ex(3)>, L<EVP_PKEY_decrypt(3)> (as well
|
||||
as other related functions).
|
||||
via the API functions L<EVP_PKEY_encrypt(3)>,
|
||||
L<EVP_PKEY_decrypt(3)> and
|
||||
other related functions).
|
||||
|
||||
All "functions" mentioned here are passed as function pointers between
|
||||
F<libcrypto> and the provider in B<OSSL_DISPATCH> arrays via
|
||||
@@ -108,7 +108,7 @@ structure for holding context information during an asymmetric cipher operation.
|
||||
A pointer to this context will be passed back in a number of the other
|
||||
asymmetric cipher operation function calls.
|
||||
The parameter I<provctx> is the provider context generated during provider
|
||||
initialisation (see L<provider(3)>).
|
||||
initialisation (see L<provider(7)>).
|
||||
|
||||
OP_asym_cipher_freectx() is passed a pointer to the provider side asymmetric
|
||||
cipher context in the I<ctx> parameter.
|
||||
|
||||
Reference in New Issue
Block a user