Home
last modified time | relevance | path

Searched refs:capable (Results 1 – 25 of 29) sorted by relevance

12

/openssl-master/providers/common/include/prov/
A Dprovider_util.h130 int (*capable)(void); member
/openssl-master/providers/common/
A Dprovider_util.c348 if (in[i].capable == NULL || in[i].capable()) in ossl_prov_cache_exported_algorithms()
/openssl-master/doc/man3/
A DSSL_get0_peer_scts.pod25 capable of sending.
A DOPENSSL_instrument_bus.pod37 Return value of 0 indicates that CPU is not capable of performing the
A DDTLSv1_listen.pod47 message thus proving that the client is capable of receiving messages sent to
55 state and thus capable of receiving messages from any peer.
A DSSL_get_all_async_fds.pod36 capable engines are in use then more than one is possible. The number of file
A DSSL_set_async_callback.pod31 B<SSL_MODE_ASYNC> has been set and an asynchronous capable engine completes a
A DOPENSSL_ia32cap.pod68 executed on SSE2 capable CPU, but under control of OS that does not
A DASYNC_start_job.pod147 can be used to detect whether the current platform is async capable or not.
165 ASYNC_is_capable() returns 1 if the current platform is async capable or 0
A DSSL_CTX_set_mode.pod105 SSL_ERROR_WANT_ASYNC with this mode set if an asynchronous capable engine is
A DSSL_CTX_set_split_send_fragment.pod60 a cipher suite is negotiated that uses a pipeline capable cipher provided by an
A DSSL_get_error.pod128 using L<SSL_CTX_set_mode(3)> or L<SSL_set_mode(3)> and an asynchronous capable
A DASYNC_WAIT_CTX_new.pod113 An example of typical usage might be an async capable engine. User code would
/openssl-master/test/recipes/30-test_evp_data/
A Devppkey_sm2.txt69 # is capable of creating a signature without failing, but it does not say
/openssl-master/doc/man7/
A Dlife_cycle-rand.pod26 This state represents the RAND when it is set up and capable of generating
32 capable of generating output.
A Dlife_cycle-mac.pod25 This state represents the MAC when it is set up and capable of processing
30 This state represents the MAC when it is set up and capable of processing
A Dlife_cycle-digest.pod24 This state represents the MD when it is set up and capable of processing
29 This state represents the MD when it is set up and capable of processing
A Dlife_cycle-kdf.pod25 This state represents the KDF/PRF when it is set up and capable of generating
A Dlife_cycle-cipher.pod25 These states represent the CIPHER when it is set up and capable of processing
40 These states represent the CIPHER when it is set up and capable of processing
/openssl-master/test/ssl-tests/
A D13-fragmentation.cnf.in160 # Test that multibuffer-capable code also handles small data correctly.
/openssl-master/doc/man1/
A Dopenssl-speed.pod.in52 TLS-like sequence. And if I<algo> is a multi-buffer capable cipher, e.g.
A Dopenssl-ecparam.pod.in130 The L<openssl-genpkey(1)> and L<openssl-pkeyparam(1)> commands are capable
A Dopenssl-dsa.pod.in145 The L<openssl-pkey(1)> command is capable of performing all the operations
A Dopenssl-rsa.pod.in157 The L<openssl-pkey(1)> command is capable of performing all the operations
A Dopenssl-ec.pod.in152 The L<openssl-pkey(1)> command is capable of performing all the operations

Completed in 31 milliseconds

12