Lines Matching +full:out +full:- +full:functions

5 provider-kem - The kem library E<lt>-E<gt> provider functions
15   * None of these are actual functions, but are displayed like this for
16   * the function signatures for functions that are offered as function
28  int OSSL_FUNC_kem_encapsulate(void *ctx, unsigned char *out, size_t *outlen,
33  int OSSL_FUNC_kem_decapsulate(void *ctx, unsigned char *out, size_t *outlen,
49 via the API functions L<EVP_PKEY_encapsulate(3)>,
50 L<EVP_PKEY_decapsulate(3)> and other related functions.
52 All "functions" mentioned here are passed as function pointers between
56 (see L<provider-base(7)/Provider Functions>).
58 All these "functions" have a corresponding function type definition
69 macros in L<openssl-core_dispatch.h(7)>, as follows:
87 functions.
88 In order to be a consistent set of functions a provider must implement
100 See L<provider-keymgmt(7)> for further details.
102 =head2 Context Management Functions
118 =head2 Asymmetric Key Encapsulation Functions
128 provider-keymgmt(7)>.
133 Unless I<out> is NULL, the data to be encapsulated is internally generated,
136 I<out> parameter. The length of the encapsulated data should be written to
140 If I<out> is NULL then the maximum length of the encapsulated data should be
144 =head2 Decapsulation Functions
152 provider-keymgmt(7)>.
159 Unless I<out> is NULL, the decapsulated data should be written to the location
160 pointed to by the I<out> parameter.
162 If I<out> is NULL then the maximum length of the decapsulated data should be
169 functions.
181 No parameters are currently recognised by built-in asymmetric kem algorithms.
193 All other functions should return 1 for success or 0 on error.
205 Copyright 2020-2021 The OpenSSL Project Authors. All Rights Reserved.