/openssl/doc/man3/ |
H A D | BIO_set_callback.pod | 8 - BIO callback functions 48 callback. The callback is called during most high-level BIO operations. It can 64 deprecated version of the same callback for use with the old callback 116 In the notes below, B<callback> defers to the actual callback 127 callback(b, BIO_CB_FREE, NULL, 0L, 0L, 1L) 137 callback(b, BIO_CB_READ, data, dlen, 0L, 1L) 156 callback(b, BIO_CB_WRITE, datat, dlen, 0L, 1L) 175 callback(b, BIO_CB_GETS, buf, size, 0L, 1L) 194 callback(b, BIO_CB_PUTS, buf, 0, 0L, 1L) 212 callback(b, BIO_CB_CTRL, parg, cmd, larg, 1L) [all …]
|
H A D | SSL_set_async_callback.pod | 20 int SSL_CTX_set_async_callback(SSL_CTX *ctx, SSL_async_callback_fn callback); 22 int SSL_set_async_callback(SSL *s, SSL_async_callback_fn callback); 30 supports the callback mechanism, it will be automatically called if 34 SSL_CTX_set_async_callback_arg() sets the callback argument. 36 SSL_set_async_callback() allows an application to set a callback in an 42 above callback is called. 58 Application sets the async callback and callback data on an SSL connection 69 async callback function would be called (goto Step 7). 84 The engine will call the application's callback passing the callback data as 89 The callback function should then run. Note: it is a requirement that the [all …]
|
H A D | SSL_CTX_set_ct_validation_callback.pod | 20 int SSL_set_ct_validation_callback(SSL *s, ssl_ct_validation_cb callback, 23 ssl_ct_validation_cb callback, 35 This is accomplished by setting a built-in CT validation callback. 47 callback. 70 and the callback returns a non-positive result. 73 the callback. 74 This will be passed to the callback whenever it is invoked. 82 In that case the handshake continues as it would had no callback been 96 enabled via either SSL_enable_ct() or a non-null custom callback, and 0 124 validation callback is set, or 0 if no callback (or equivalently a NULL [all …]
|
H A D | SSL_CTX_set_psk_client_callback.pod | 11 - set PSK client callback 45 The callback function is given a pointer to the SSL connection in B<ssl>. 98 this the callback should return successfully and ensure that B<*sess> is 105 The purpose of the callback function is to select the PSK identity and 108 The callback is set using functions SSL_CTX_set_psk_client_callback() 109 or SSL_set_psk_client_callback(). The callback function is given the 127 B<SSL_psk_use_session_cb_func> callback, and are not possible with the 128 B<SSL_psk_client_cb_func> callback. 132 Note that parameter B<hint> given to the callback may be B<NULL>. 150 On success (callback found a PSK identity and a pre-shared key to use) [all …]
|
H A D | SSL_CTX_use_psk_identity_hint.pod | 42 A server application wishing to use TLSv1.3 PSKs should set a callback 46 The callback function is given a pointer to the SSL connection in B<ssl> and 47 an identity in B<identity> of length B<identity_len>. The callback function 55 callback should return successfully and ensure that B<*sess> is 69 callback function which is called when the server receives the 72 during the connection setup phase. The callback is set using the functions 78 The callback for use in TLSv1.2 will also work in TLSv1.3 although it is 88 callback, and are not possible with the B<SSL_psk_server_cb_func> callback. 110 PSK identity was found and the server callback has provided the PSK 115 If the PSK identity was not found but the callback instructs the [all …]
|
H A D | SSL_set_session_secret_cb.pod | 6 - set the session secret callback 22 SSL_set_session_secret_cb() sets the session secret callback to be used 24 callback when it is called. This is only useful for an implementation of 25 EAP-FAST (RFC4851). The presence of the callback also modifies the internal 27 RFC4851. Therefore this callback should not be used except when implementing 30 The callback is expected to set the master secret to be used by filling in the 32 available in I<*secret_len> and may be updated by the callback (but must not be 36 the I<peer_ciphers> stack. Optionally the callback may select the preferred 39 On the client side the I<peer_ciphers> stack will always be NULL. The callback 44 The callback is also supplied with an additional argument in I<arg> which is the [all …]
|
H A D | OSSL_SELF_TEST_set_callback.pod | 6 OSSL_SELF_TEST_get_callback - specify a callback for processing self tests 17 Set or gets the optional application callback (and the callback argument) that 19 The application callback L<OSSL_CALLBACK(3)> is associated with a B<OSSL_LIB_CTX>. 20 The application callback function receives information about a running self test, 22 See L<openssl-core.h(7)> for further information on the callback. 26 OSSL_SELF_TEST_get_callback() returns the callback and callback argument that
|
H A D | SSL_CTX_set_info_callback.pod | 9 - handle information callback for SSL connections 21 void (*callback) (const SSL *ssl, int type, int val)); 27 SSL_CTX_set_info_callback() sets the B<callback> function, that can be used to 31 When B<callback> is NULL, no callback function is used. 33 SSL_set_info_callback() sets the B<callback> function, that can be used to 35 When B<callback> is NULL, the callback setting currently valid for 39 callback function for B<ctx>. 42 callback function for B<ssl>. 51 The callback function is called as B<callback(SSL *ssl, int where, int ret)>. 53 the callback function was called. If B<ret> is 0, an error condition occurred. [all …]
|
H A D | SSL_CTX_set_cert_verify_callback.pod | 12 int (*callback)(X509_STORE_CTX *, void *), 17 SSL_CTX_set_cert_verify_callback() sets the verification callback function for 27 If a verification callback I<callback> is specified via 28 SSL_CTX_set_cert_verify_callback(), the supplied callback function is called 30 The argument I<arg> is specified by the application when setting I<callback>. 31 By setting I<callback> to NULL, the default behaviour is restored. 33 I<callback> should return 1 to indicate verification success 42 In client mode I<callback> may also call the L<SSL_set_retry_verify(3)> 57 the I<callback> allows the connection to continue (by returning 1). 66 Within I<x509_store_ctx>, I<callback> has access to the I<verify_callback> [all …]
|
H A D | SSL_CTX_set_cert_cb.pod | 5 SSL_CTX_set_cert_cb, SSL_set_cert_cb - handle certificate callback function 17 SSL_CTX_set_cert_cb() and SSL_set_cert_cb() sets the I<cert_cb> callback, 18 I<arg> value is pointer which is passed to the application callback. 20 When I<cert_cb> is NULL, no callback function is used. 22 I<cert_cb> is the application defined callback. It is called before a 23 certificate will be used by a client or server. The callback can then inspect 25 the callback is successful it B<MUST> return 1 even if no certificates have 45 The certificate callback functionality supersedes the (largely broken) 46 functionality provided by the old client certificate callback interface. 50 A more advanced callback might examine the handshake parameters and set [all …]
|
H A D | SSL_CTX_set_keylog_callback.pod | 19 SSL_CTX_set_keylog_callback() sets the TLS key logging callback. This callback 24 callback. If no callback has been set, this will return NULL. When there is no 25 key logging callback, or if SSL_CTX_set_keylog_callback is called with NULL as 28 The key logging callback is called with two items: the B<ssl> object associated 31 file, the key logging callback should log B<line>, followed by a newline. 37 NULL if the callback is not set.
|
H A D | OSSL_SELF_TEST_new.pod | 9 OSSL_SELF_TEST_onend - functionality to trigger a callback during a self test 29 callback and callback argument associated with it. 39 If this method is called the callback I<cb> will receive the following 52 passed in array of I<bytes> will be corrupted if the callback returns 0, 56 If this method is called the callback I<cb> will receive the following 70 If this method is called the callback I<cb> will receive the following 82 After the callback I<cb> has been called the values that were set by 87 passed to the callback. 94 This allows the callback to identify the type of test being run. 132 /* Trigger the optional callback */ [all …]
|
H A D | X509_STORE_CTX_set_verify_cb.pod | 21 - get and set X509_STORE_CTX components such as verification callback 55 X509_STORE_CTX_set_verify_cb() sets the verification callback of B<ctx> to 56 B<verify_cb> overwriting any existing callback. 65 The B<ok> parameter to the callback indicates the value the callback should 71 The B<ctx> parameter to the callback is the B<X509_STORE_CTX> structure that 72 is performing the verification operation. A callback can examine this 75 be passed to the callback via the B<ex_data> mechanism. 77 X509_STORE_CTX_print_verify_cb() is a verification callback function that, 83 X509_STORE_CTX_get_verify_cb() returns the value of the current callback 103 X509_STORE_CTX_get_crl_fn. The X509_STORE_CTX_get_crl_fn callback must [all …]
|
H A D | SSL_CTX_set_alpn_select_cb.pod | 61 the application callback. 81 callback or the NPN callback (described below). If no match is found, the first 91 For the callback itself, B<out> 95 callback can assume that B<in> is syntactically valid. The client must 97 fatal to the connection if this callback returns a value other than 107 reference to it. The callback should return B<SSL_TLSEXT_ERR_OK> if it 121 provided by the callback. 144 The ALPN callback is executed after the servername callback; as that servername 145 callback may update the SSL_CTX, and subsequently, the ALPN callback. 171 The ALPN select callback B<cb>, must return one of the following: [all …]
|
H A D | OSSL_INDICATOR_set_callback.pod | 6 OSSL_INDICATOR_get_callback - specify a callback for FIPS indicators 22 OSSL_INDICATOR_set_callback() sets a user callback I<cb> associated with a 25 The user's callback may be triggered multiple times during an algorithm operation 32 The user's callback B<OSSL_INDICATOR_CALLBACK> I<type> and I<desc> 36 If the user callback returns 0, an error will occur in the caller. This can be 41 OSSL_INDICATOR_get_callback() returns the callback that has been set via 43 if no callback is currently set. 47 A simple indicator callback to log non approved FIPS operations
|
H A D | SSL_CTX_set_client_cert_cb.pod | 19 SSL_CTX_set_client_cert_cb() sets the I<client_cert_cb> callback, that is 23 When I<client_cert_cb> is NULL, no callback function is used. 25 SSL_CTX_get_client_cert_cb() returns a pointer to the currently set callback 28 I<client_cert_cb> is the application defined callback. If it wants to 51 library. Using the callback function it is possible to implement a proper 55 If a callback function is defined and no certificate was yet defined for the 56 SSL object, the callback function will be called. 57 If the callback function returns a certificate, the OpenSSL library 62 If the callback returns no certificate, the OpenSSL library will not send 68 NULL if the callback is not set. [all …]
|
H A D | SSL_CTX_set_client_hello_cb.pod | 30 The argument supplied when setting the callback is passed back to the 31 callback at run time. A callback that returns failure (0) will cause the 33 what alert value is to be sent in the B<al> parameter. A callback may 39 function, the ClientHello callback will be called again, and, if it returns 90 code to affect the TLS handshake. A primary use of the callback is to 99 It is also recommended that applications utilize a ClientHello callback and 100 not use a servername callback, in order to avoid unexpected behavior that 102 resumption and the historical servername callback. 105 within a ClientHello callback. 109 The application's supplied ClientHello callback returns [all …]
|
H A D | SSL_CTX_sess_set_get_cb.pod | 5 …t_new_cb, SSL_CTX_sess_get_remove_cb, SSL_CTX_sess_get_get_cb - provide callback functions for ser… 31 SSL_CTX_sess_set_new_cb() sets the callback function that is 34 SSL_CTX_sess_set_remove_cb() sets the callback function that is 39 SSL_CTX_sess_set_get_cb() sets the callback function that is called 47 corresponding set callback functions. If a callback function has not been 53 session cache is realized via callback functions. Inside these callback 62 session is incremented before the callback, on behalf of the application. If 63 the callback returns B<0>, the session will be immediately removed from the 64 internal cache and the reference count released. If the callback returns B<1>, 94 B<data>. By setting the parameter B<copy> to B<1>, the callback can require the [all …]
|
H A D | BN_generate_prime.pod | 33 int (*callback)(int, int, BN_GENCB *), void *cb_arg); 177 to BN_GENCB_set_old() and B<callback> is of type 178 B<void (*callback)(int, int, void *)>. 181 the type of the callback and will invoke B<callback(a, b, gencb)> for new 182 style callbacks or B<callback(a, b, cb_arg)> for old style. 188 BN_generate_prime_ex() but expects an old-style callback function 220 BN_GENCB callback; 224 BN_GENCB *callback; 225 callback = BN_GENCB_new(); 226 if (!callback) [all …]
|
H A D | SSL_CTX_set_session_ticket_cb.pod | 32 with a session, and placed into a session ticket. Either callback function may 35 B<gen_cb> is the application defined callback invoked when a session ticket is 39 callback is defined as type B<SSL_CTX_generate_session_ticket_fn>. 41 B<dec_cb> is the application defined callback invoked after session ticket 48 B<dec_cb> callback is defined as type B<SSL_CTX_decrypt_session_ticket_fn>. 122 If the callback does not wish to change the default ticket behaviour then it 129 the callback to return this value if B<status> has a value other than 138 callback to return this value if B<status> has a value other than 147 no session data will be available and the callback must not use the B<ss> 159 this behaviour can be changed if a ticket key callback is in use (see [all …]
|
H A D | SSL_CTX_set_default_passwd_cb.pod | 9 get passwd callback for encrypted PEM file handling 27 SSL_CTX_set_default_passwd_cb() sets the default password callback called 31 which will be provided to the password callback on invocation. 34 callback currently set in B<ctx>. If no callback was explicitly set, the 45 The password callback, which must be provided by the application, hands back the 51 callback is used for reading/decryption (rwflag=0) or writing/encryption 60 to have the callback handle the password dialog interactively. If several 64 callback only returns the password already stored. 66 When asking for the password interactively, the callback can use
|
H A D | SSL_CTX_set_record_padding_callback.pod | 14 SSL_set_block_padding_ex - install callback to specify TLS 1.3 record padding 37 can be used to assign a callback function I<cb> to specify the padding 39 Kernel TLS is not possible if the record padding callback is set, and the callback 43 assign a value B<arg> that is passed to the callback when it is invoked. The value 47 retrieve the B<arg> value that is passed to the callback. 57 The callback is invoked for every record before encryption. 82 the callback function is not set because Kernel TLS is configured for the SSL object. 88 A user-supplied padding callback function will override the behavior set by 90 callback to NULL will restore the configured block padding behavior.
|
/openssl/crypto/bn/ |
H A D | bn_depr.c | 24 void (*callback) (int, int, void *), void *cb_arg) in BN_generate_prime() 29 BN_GENCB_set_old(&cb, callback, cb_arg); in BN_generate_prime() 47 void (*callback) (int, int, void *), BN_CTX *ctx_passed, in BN_is_prime() 51 BN_GENCB_set_old(&cb, callback, cb_arg); in BN_is_prime() 56 void (*callback) (int, int, void *), in BN_is_prime_fasttest() 61 BN_GENCB_set_old(&cb, callback, cb_arg); in BN_is_prime_fasttest()
|
/openssl/test/ssl-tests/ |
H A D | 03-custom_verify.cnf.in | 17 # restrictive callback. 25 # Same test as above but with a custom callback that always fails. 40 # Same test as above but with a custom callback that always succeeds. 54 # Same test as above but with a custom callback that requests retry once. 80 # Same test as above but with a custom callback that always fails. 81 # The callback return has no impact on handshake success in this mode. 97 # Same test as above but with a custom callback that always succeeds. 98 # The callback return has no impact on handshake success in this mode. 115 # permissive callback. 129 # Same test as above but with a custom callback that always succeeds. [all …]
|
/openssl/crypto/async/ |
H A D | async_wait.c | 184 ASYNC_callback_fn callback, in ASYNC_WAIT_CTX_set_callback() argument 190 ctx->callback = callback; in ASYNC_WAIT_CTX_set_callback() 196 ASYNC_callback_fn *callback, in ASYNC_WAIT_CTX_get_callback() argument 199 if (ctx->callback == NULL) in ASYNC_WAIT_CTX_get_callback() 202 *callback = ctx->callback; in ASYNC_WAIT_CTX_get_callback()
|