Searched refs:ready (Results 1 – 24 of 24) sorted by relevance
/openssl/doc/man3/ |
H A D | ASYNC_start_job.pod | 96 know when a job is ready to be restarted. 122 applications that a job is ready to be resumed. One is a "wait" file 126 applications to wait for the file descriptor to be ready for "read" using a 127 system function call such as select(2) or poll(2) (being ready for "read" 131 it to see if it is ready to continue. 244 * Create a way to inform the calling thread when this job is ready 264 * Normally some external event (like a network read being ready, 268 * immediately signalling that the job is ready to be woken up after 275 * method. The main thread will wait until pipefds[0] is ready 321 * to be ready to be woken up [all …]
|
H A D | ASYNC_WAIT_CTX_new.pod | 91 Applications can wait for the file descriptor to be ready for "read" using a 92 system function call such as select or poll (being ready for "read" indicates 95 to see if it is ready to continue. 117 perform other tasks or wait for the job to be ready by calling "select" or other
|
H A D | DTLSv1_listen.pod | 112 will be set up ready to continue the handshake. A return value of 0 or -1 117 will be set up ready to continue the handshake. the B<peer> value will also be
|
H A D | SSL_get_all_async_fds.pod | 31 appearing as "read ready" on the file descriptor (no actual data should be read
|
H A D | EVP_PKEY_set1_encoded_public_key.pod | 74 =head2 Set up a peer's EVP_PKEY ready for a key exchange operation
|
H A D | PKCS7_sign.pod | 65 just initialized ready to perform the signing operation. The signing is however
|
H A D | CMS_sign.pod | 79 structure is just initialized ready to perform the signing operation. The
|
H A D | EVP_RAND.pod | 220 The instantiate call will change this to the ready state. 224 EVP_RAND_STATE_READY: this RNG is currently ready to generate output.
|
H A D | OSSL_HTTP_transfer.pod | 69 As soon as the client has flushed I<bio> the server must be ready to provide
|
H A D | SSL_poll.pod | 345 before any resource was ready.
|
H A D | ENGINE_add.pod | 213 is ready to perform cryptographic operations, and will remain initialised
|
/openssl/util/perl/TLSProxy/ |
H A D | Proxy.pm | 411 my @ready; 422 if (!(@ready = $fdset->can_read(1))) { 429 foreach my $hand (@ready) {
|
/openssl/doc/man7/ |
H A D | life_cycle-pkey.pod | 24 This state represents the PKEY when it is ready to perform a private key decapsulation 29 This state represents the PKEY when it is ready to decrypt some ciphertext. 33 This state represents the PKEY when it is ready to derive a shared secret. 37 This state represents the PKEY when it is ready to perform a private key signature 42 This state represents the PKEY when it is ready to perform a public key encapsulation 47 This state represents the PKEY when it is ready to encrypt some plaintext. 51 This state represents the PKEY when it is ready to generate a new public/private key. 55 This state represents the PKEY when it is ready to generate key parameters. 59 This state represents the PKEY when it is ready to verify a public key signature. 63 This state represents the PKEY when it is ready to recover a public key signature data.
|
H A D | ossl-guide-tls-server-block.pod | 269 And now we're ready to attempt the SSL handshake. With a blocking socket 301 The server is now ready to accept the next client connection. 306 be ready to exit, it would first deallocate the constructed B<SSL_CTX>.
|
H A D | ossl-guide-libcrypto-introduction.pod | 279 operation is then initialised ready for use via an "init" function - optionally
|
H A D | ossl-guide-tls-client-block.pod | 432 Once we have finished reading data from the server then we are ready to close
|
/openssl/test/ |
H A D | quic_multistream_test.c | 107 int ready, stop; member 568 int ready, stop; in server_helper_thread() local 570 ready = h->server_thread.ready; in server_helper_thread() 576 if (!ready) { in server_helper_thread() 1106 else if (h->blocking && !h->server_thread.ready) { in run_script_worker() 1108 h->server_thread.ready = 1; in run_script_worker()
|
/openssl/doc/designs/quic-design/ |
H A D | quic-tls.md | 23 established, crypto frame data is ready to be sent or consumed, or when the
|
H A D | quic-io-arch.md | 167 therefore important to only generate packets when they are ready to be sent, 392 plumbed in for socket handles, and so sockets are simply never considered ready
|
H A D | glossary.md | 7 **Active Stream:** A stream which has data or control frames ready for
|
H A D | quic-fault-injector.md | 71 called after each handshake message has been constructed and is ready to send, but
|
H A D | connection-state-machine.md | 110 Handshake EL is ready.
|
H A D | tx-packetiser.md | 254 - Active Stream: A stream which has data or flow control frames ready for
|
/openssl/ |
H A D | CHANGES.md | 6822 those messages that OpenSSL is not yet ready to process will be buffered 8023 those messages that OpenSSL is not yet ready to process will be buffered
|
Completed in 92 milliseconds