Searched refs:context (Results 251 – 275 of 342) sorted by relevance
1...<<11121314
/openssl/include/openssl/ |
H A D | tls1.h | 262 const unsigned char *context, 275 const unsigned char *context,
|
/openssl/doc/man3/ |
H A D | SMIME_write_ASN1.pod | 33 The library context I<libctx> and the property query I<propq> are used when
|
H A D | EVP_PKEY_CTX_set_tls1_prf_md.pod | 49 A context for the TLS PRF can be obtained by calling:
|
H A D | EVP_PKEY_CTX_set_rsa_pss_keygen_md.pod | 79 A context for the B<RSA-PSS> algorithm can be obtained by calling:
|
H A D | EVP_SealInit.pod | 25 EVP_SealInit() initializes a cipher context B<ctx> for encryption
|
H A D | SRP_Calc_B.pod | 68 context and property query string. The SRP_Calc_server_key() and SRP_Calc_A()
|
H A D | EVP_PKEY_get_size.pod | 58 that this function call delivers in the context that it's called in.
|
H A D | SSL_set_async_callback.pod | 90 callback function is small and nonblocking as it will be run in the context of
|
H A D | SSL_CTX_set_cert_verify_callback.pod | 58 Note that the verification status in the store context is a possibly durable
|
H A D | EVP_KEYEXCH_free.pod | 69 all activated providers in the library context I<libctx>, and for each
|
H A D | OSSL_CMP_validate_msg.pod | 24 In the former case a suitable trust anchor must be given in the CMP context
|
H A D | EVP_SIGNATURE.pod | 64 activated providers in the given library context I<libctx>, and for each of the
|
H A D | EVP_PKEY_new.pod | 95 the library context I<libctx> and the property query string I<propq>. The 105 EVP_PKEY_new_raw_private_key_ex() except that the default library context and
|
/openssl/doc/internal/man3/ |
H A D | evp_pkey_export_to_provider.pod | 27 default context), the name of the legacy type of I<pk>, and the I<propquery>
|
H A D | ossl_cmp_mock_srv_new.pod | 45 associated with the library context I<libctx> and property query string
|
/openssl/doc/man7/ |
H A D | EVP_PKEY-X25519.pod | 91 An B<EVP_PKEY> context can be obtained by calling:
|
H A D | EVP_KDF-X963.pod | 81 A context for X963KDF can be obtained by calling:
|
H A D | EVP_KEYEXCH-ECDH.pod | 19 In the context of an Elliptic Curve Diffie-Hellman key exchange, this parameter
|
H A D | EVP_PKEY-DSA.pod | 65 An B<EVP_PKEY> context can be obtained by calling:
|
H A D | proxy-certificates.pod | 165 ex_data store that is attached to an X509 validation context. 188 * store in the X509 validation context the first time it's
|
H A D | provider.pod | 67 I<*provctx> should be assigned a provider specific context to allow 85 I<provctx> is the provider specific context that was passed back by
|
/openssl/ssl/ |
H A D | ssl_local.h | 1999 unsigned int context; member 2758 const unsigned char *context, 2763 const unsigned char *context, 2907 unsigned int context, 2913 __owur int custom_ext_parse(SSL_CONNECTION *s, unsigned int context, 2917 __owur int custom_ext_add(SSL_CONNECTION *s, int context, WPACKET *pkt, X509 *x,
|
/openssl/doc/designs/ |
H A D | thread-api.md | 54 As usual, `ctx` can be NULL to use the default library context.
|
/openssl/doc/designs/quic-design/ |
H A D | quic-requirements.md | 91 treated separately by our APIs. In the context of QUIC, APIs to be able to 97 effectively they are single stream in nature) and this fundamental context of
|
/openssl/crypto/engine/ |
H A D | README.md | 98 EVP_CIPHER_CTX context, and the EVP_CIPHER structure is left hooked into the 99 context and so is used as the implementation. Pretty much how things work now 105 That functional reference will be stored in the context (and released on
|
Completed in 53 milliseconds
1...<<11121314