| /openssl/doc/man3/ |
| H A D | SSL_COMP_add_compression_method.pod | 7 - handle SSL/TLS integrated compression methods
|
| H A D | X509_ACERT_get0_holder_baseCertId.pod | 59 possible. It is up to the application to handle cases when conflicting
|
| H A D | OSSL_PROVIDER.pod | 71 The functions described here handle both forms.
156 provider. The provider context is an opaque handle set by the provider itself
|
| H A D | ASYNC_start_job.pod | 90 ASYNC_pause_job() below). A handle to the job is placed in I<*job>. Other work
92 a job call ASYNC_start_job() again passing the job handle in I<*job>. The
247 * the ENGINE should handle that internally.
|
| H A D | SSL_CTX_set_default_passwd_cb.pod | 60 to have the callback handle the password dialog interactively. If several
|
| H A D | EVP_PKEY_copy_parameters.pod | 46 EVP_PKEY_copy_parameters() is to handle public keys in certificates where the
|
| H A D | BIO_get_rpoll_descriptor.pod | 61 The resource is whatever kind of handle is used by a given OS to represent
|
| H A D | BIO_get_ex_new_index.pod | 85 These functions handle application-specific data for OpenSSL data
|
| H A D | ASN1_TYPE_get.pod | 74 applications should handle the case of two absent values separately.
|
| H A D | EVP_PKEY_decrypt.pod | 69 rejection, the code still needs to handle the returned values
|
| H A D | PEM_read_bio_PrivateKey.pod | 233 handle traditional and PKCS#8 format encrypted and unencrypted keys.
310 handle either form so there are no B<X509_REQ_NEW> read functions.
370 (for example a window handle in a GUI application). The callback
395 they handle all formats transparently.
|
| H A D | SSL_CTX_set_client_cert_cb.pod | 5 SSL_CTX_set_client_cert_cb, SSL_CTX_get_client_cert_cb - handle client certificate callback function
|
| H A D | X509_NAME_print_ex.pod | 42 produce a non standard output form, they don't handle multi-character fields and
|
| H A D | OSSL_DECODER.pod | 48 of OpenSSL knows how to handle.
|
| H A D | RSA_public_encrypt.pod | 104 handle the returned values using side-channel free code.
|
| H A D | DSA_get0_pqg.pod | 83 DSA_get0_engine() returns a handle to the ENGINE that has been set for this DSA
|
| /openssl/test/ |
| H A D | tls-provider.c | 55 int tls_provider_init(const OSSL_CORE_HANDLE *handle,
3215 int tls_provider_init(const OSSL_CORE_HANDLE *handle, in tls_provider_init() argument
3220 OSSL_LIB_CTX *libctx = OSSL_LIB_CTX_new_from_dispatch(handle, in); in tls_provider_init()
3259 if (!c_obj_create(handle, XORSIGALG_OID, XORSIGALG_NAME, XORSIGALG_NAME)) { in tls_provider_init()
3264 if (!c_obj_add_sigid(handle, XORSIGALG_OID, "", XORSIGALG_OID)) { in tls_provider_init()
3268 if (!c_obj_create(handle, XORSIGALG_HASH_OID, XORSIGALG_HASH_NAME, NULL)) { in tls_provider_init()
3273 if (!c_obj_add_sigid(handle, XORSIGALG_HASH_OID, XORSIGALG_HASH, XORSIGALG_HASH_OID)) { in tls_provider_init()
|
| H A D | fake_rsaprov.c | 730 static int fake_rsa_provider_init(const OSSL_CORE_HANDLE *handle, in fake_rsa_provider_init() argument
|
| /openssl/doc/man7/ |
| H A D | provider-mac.pod | 151 can handle, respectively. OSSL_FUNC_mac_gettable_ctx_params() and
157 All MAC implementations are expected to handle the following parameters:
|
| H A D | bio.pod | 17 I/O it can transparently handle SSL connections, unencrypted network
|
| H A D | provider-cipher.pod | 147 It is the responsibility of the cipher implementation to handle input lengths
203 can handle, respectively. OSSL_FUNC_cipher_gettable_ctx_params() and
|
| /openssl/doc/designs/ |
| H A D | thread-api.md | 9 - Some transports (e.g. QUIC, DTLS) may need to handle timer events
|
| /openssl/test/recipes/30-test_evp_data/ |
| H A D | evpmac_poly1305.txt | 40 # If one uses 130-bit partial reduction, does the code handle the case where partially reduced fina…
|
| /openssl/crypto/property/ |
| H A D | README.md | 61 contains some wrapper functions to handle the global
|
| /openssl/doc/designs/quic-design/ |
| H A D | record-layer.md | 22 Within the TLS record layer there are options to handle "multiblock" and
25 have to be able to handle different protocol versions.
215 data contained in it. Each record has an associated opaque handle `rechandle`.
502 * An opaque record layer handle for the record is returned in |*rechandle|
|
