Searched refs:existing (Results 1 – 25 of 133) sorted by relevance
123456
/openssl/doc/man3/ |
H A D | ADMISSIONS.pod | 120 functions free any existing value and set the pointer to the specified value. 130 functions free any existing value and set the pointer to the specified value. 141 functions free any existing value and set the pointer to the specified value. 157 functions free any existing value and set the pointer to the specified value.
|
H A D | SSL_load_client_CA_file.pod | 37 and adds their subject name to the already existing I<stack>. 41 already existing I<stack>. 44 I<store> URI, and adds their subject name to the already existing
|
H A D | PKCS8_pkey_add1_attr.pod | 25 existing PKCS8_PRIV_KEY_INFO structure B<p8>. 28 X509_ATTRIBUTE from the passed arguments and add it to the existing
|
H A D | SSL_CTX_set_ctlog_list_file.pod | 26 These functions will not clear the existing CT log list - it will be appended 27 to. To replace the existing list, use L<SSL_CTX_set0_ctlog_store(3)> first.
|
H A D | BUF_MEM_new.pod | 35 BUF_MEM_free() frees up an already existing buffer. The data is zeroed 39 BUF_MEM_grow() changes the size of an already existing buffer to
|
H A D | SSL_CTX_add1_chain_cert.pod | 51 SSL_CTX_clear_chain_certs() clears any existing chain associated with the 58 If the function is successful the built chain will replace any existing chain. 60 existing chain certificates as untrusted CAs, B<SSL_BUILD_CHAIN_FLAG_NO_ROOT> 62 use all existing chain certificates only to build the chain (effectively
|
H A D | EVP_PKEY_CTX_set_hkdf_md.pod | 74 buffer B<salt>. Any existing value is replaced. 77 B<key>. Any existing value is replaced. 80 buffer B<info>. If a value is already set, it is appended to the existing
|
H A D | EVP_PKEY_CTX_set_tls1_prf_md.pod | 30 to B<seclen> bytes of the buffer B<sec>. Any existing secret value is replaced 34 If a seed is already set it is appended to the existing value.
|
H A D | HMAC.pod | 84 HMAC_CTX_reset() clears an existing B<HMAC_CTX> and associated 98 existing key is 104 because reuse of an existing key with a different digest is not supported.
|
H A D | X509_ACERT_add_attr_nconf.pod | 18 existing B<X509_ACERT> structure I<acert>. The attributes are read
|
H A D | X509V3_get_d2i.pod | 103 B<X509V3_ADD_REPLACE> replaces an existing extension. If the extension does 106 B<X509V3_ADD_REPLACE_EXISTING> replaces an existing extension. If the 112 B<X509V3_ADD_DELETE> deletes and frees an existing extension. If the extension
|
H A D | PKCS12_add1_attr_by_NID.pod | 29 These functions do not check whether an existing attribute of the same type is
|
H A D | ASN1_INTEGER_get_int64.pod | 64 the existing structure will be used instead. 68 existing structure will be used instead.
|
H A D | EVP_CIPHER_CTX_get_cipher_data.pod | 25 replace the cipher data with new data. A pointer to any existing cipher data is
|
/openssl/doc/internal/man3/ |
H A D | DEFINE_LIST_OF.pod | 38 void ossl_list_TYPE_insert_before(OSSL_LIST(name) *list, type *existing, 40 void ossl_list_TYPE_insert_after(OSSL_LIST(name) *list, type *existing, type *elem); 87 I<existing> element. 91 I<existing> element.
|
H A D | ossl_DER_w_precompiled.pod | 18 There may be already existing DER blobs that can simply be copied to
|
/openssl/doc/designs/quic-design/ |
H A D | quic-requirements.md | 23 intrusive, more maintainable, and to harmonize the existing record layer 87 existing (or future) security protocols and to select between them with minimal 96 * The majority of existing applications operate using a single connection (i.e. 100 * We need to enable the majority of our existing user’s applications to be able 133 * High performance applications (primarily server based) using existing libssl 136 using fibres). Would prefer to use the existing APIs - they don’t want to throw
|
H A D | quic-statm.md | 52 `OSSL_TIME_ZERO`, the existing Latest RTT value is used when updating the
|
H A D | error-handling.md | 24 We need to keep using the existing ERR API as doing otherwise would 25 complicate the existing applications and break our API compatibility promise.
|
/openssl/doc/designs/ |
H A D | fips_indicator.md | 29 Since any new FIPS restrictions added could possibly break existing applications 40 In OpenSSL most of the existing code in the FIPS provider is using 41 implicit indicators i.e. An error occurs if existing FIPS rules are violated. 46 …s a change. These options will be passed to the FIPS provider in a manner similar to existing code. 142 the existing code needs to change to work with indicators. 144 e.g. existing code 181 in existing behaviour. For example the keysize checks are done in the init since 252 Some existing algorithms will require set_ctx_params()/settable_ctx_params()
|
H A D | xof.md | 39 considering how the change may affect existing applications. 87 - The existing function does not change, so it is not affected by logic that 89 - The behaviour of the existing API is the same. 185 The existing one shot squeeze method is:
|
/openssl/ |
H A D | README-ENGINES.md | 14 users who need to maintain or support existing ENGINE implementations. 16 via providers, and existing engines should be converted to providers 43 the ENGINE model so that alternative implementations of existing 60 NCONF) code so that applications using OpenSSL's existing configuration 74 moreover, they are needed in the same POD format the existing OpenSSL 135 applications. This could be because existing compiled-in implementations 136 have known problems and you wish to use a newer version with an existing
|
H A D | HACKING.md | 7 either add a prototype in one of the existing OpenSSL header files;
|
H A D | CONTRIBUTING.md | 84 either be added to an existing test, or completely new. Please see 96 Have a look through existing entries for inspiration.
|
/openssl/doc/designs/ddd/ |
H A D | WINDOWS.md | 44 Evaluation of the existing demos and their applicability to Windows IOCP: 60 we might say here that any existing application using BIO_s_sock
|
Completed in 34 milliseconds
123456