Home
last modified time | relevance | path

Searched refs:create (Results 76 – 100 of 181) sorted by relevance

12345678

/openssl/doc/man7/
H A Dprovider-keymgmt.pod220 OSSL_FUNC_keymgmt_new() should create a provider side key object. The
232 OSSL_FUNC_keymgmt_gen_init() should create the key object generation context
346 from I<keydata>, create an L<OSSL_PARAM(3)> array with them and call
370 I<selection> or the whole key data I<keydata_from> and create a new
H A Dfips_module.pod38 Any functions that create or modify custom "METHODS" (for example
311 create two library contexts. In one we assume the existence of a config file
384 library context for FIPS usage, and just create one additional library context
430 In this first example we create two SSL_CTX objects using two different library
445 In this second example we create two SSL_CTX objects using different properties
H A Dbio.pod41 and frequently a utility function exists to create and initialize such BIOs.
H A Devp.pod29 asymmetric algorithms. To create a new EVP_PKEY see
H A Dproxy-certificates.pod119 You can also create a proxy certificate using another proxy
187 * The following procedure will create an index for the ex_data
H A Dossl-guide-quic-introduction.pod32 allowing application protocols built on QUIC to create arbitrarily many
101 create a background thread and will regularly call L<SSL_handle_events(3)> in a
H A Dprovider-decoder.pod48 The DECODER operation is a generic method to create a provider-native
64 The last decoding step in the decoding chain is usually supposed to create
H A Dossl-guide-libraries-introduction.pod69 If an application does not explicitly create a library context then the
248 You can use this if you create your own library context and want to ensure that
260 Applications that create their own library contexts may optionally configure
H A Dprovider-encoder.pod229 implementation should be able to import that array and create a suitable
233 given with I<selection> to create a provider-native object that can be
/openssl/doc/man3/
H A DPKCS7_encrypt.pod6 - create a PKCS#7 envelopedData structure
H A DEVP_PKEY_set1_encoded_public_key.pod32 set as part of this operation, so typically an application will create an
H A DOSSL_trace_enabled.pod85 calls surrounding the trace output create a group, which acts as a
231 that placing them inside a (critical) trace section would create too much
H A DBN_generate_prime.pod217 As of OpenSSL 1.1.0 it is no longer possible to create a BN_GENCB structure
222 Instead applications should create a BN_GENCB structure using BN_GENCB_new:
H A DSSL_CTX_set_client_cert_cb.pod92 and create a new one to return to the previous state.
H A DCMS_encrypt.pod5 CMS_encrypt_ex, CMS_encrypt - create a CMS envelopedData structure
/openssl/doc/internal/man3/
H A DOSSL_SAFE_MATH_SIGNED.pod8 - create helper functions to safely perform non-overflowing integer operations
/openssl/doc/internal/man7/
H A DDERlib.pod11 solely constituted of functions that work as building blocks to create
/openssl/doc/designs/
H A Dthread-api.md34 * If the argument is 0, thread pooling is disabled. OpenSSL will not create any
/openssl/doc/man1/
H A Dopenssl-crl.pod.in157 Ideally it should be possible to create a CRL using appropriate options
/openssl/test/recipes/
H A D90-test_store.t313 }, create => 1, cleanup => 1;
/openssl/crypto/conf/
H A Dconf_lib.c189 ret = meth->create(meth); in NCONF_new_ex()
/openssl/
H A DNOTES-ANDROID.md68 Another option is to create so called "standalone toolchain" tailored
/openssl/test/
H A DREADME-dev.md102 * create a three line description of how to build the test, you will have
/openssl/apps/include/
H A Dapps.h233 BIGNUM *load_serial(const char *serialfile, int *exists, int create,
/openssl/doc/designs/quic-design/
H A Dquic-fault-injector.md212 * keyfile, create a server and client instances as well as a fault injector
226 * Run the TLS handshake to create a QUIC connection between the client and
395 might be used to create tests.

Completed in 71 milliseconds

12345678