Searched refs:handle (Results 126 – 150 of 169) sorted by relevance
1234567
| /openssl/doc/man3/ |
| H A D | ENGINE_add.pod | 294 will operate with a NULL ENGINE handle - this usually equates to using the
341 probably numerous other ways in which applications may prefer to handle
500 itself and it will intercept and handle these control commands on behalf of the
|
| H A D | EC_KEY_new.pod | 117 EC_KEY_get0_engine() returns a handle to the ENGINE that has been set for
|
| H A D | SSL_get_error.pod | 116 SSL_peek(), SSL_write_ex(), and SSL_write() will handle any pending handshakes.
|
| H A D | BIO_f_ssl.pod | 301 be modified to handle this fix or they may free up an already freed BIO.
|
| H A D | OSSL_CMP_exec_certreq.pod | 123 We take "accepted" and "grantedWithMods" as clear success and handle
|
| H A D | EVP_PKEY_verify.pod | 101 handle either mode of operation, depending on if the operation was initialized
|
| H A D | EVP_PKEY_sign.pod | 106 expected to handle either mode of operation, depending on if the operation was
|
| H A D | EVP_PKEY_meth_new.pod | 283 handle the parameter generation process.
|
| H A D | X509_STORE_CTX_get_error.pod | 62 It may be examined by a verification callback invoked to handle each error
|
| /openssl/doc/designs/quic-design/ |
| H A D | quic-requirements.md | 92 handle a collection of streams will be necessary for many applications. With the
|
| H A D | quic-tls.md | 214 expects to request data from the record layer, get a handle on that data, and
|
| H A D | glossary.md | 61 **FIFD:** Frame-in-flight dispatcher. Ties together the CFQ and TXPIM to handle
|
| H A D | quic-fc.md | 71 process incoming data, but also at a rate the application can handle.
|
| H A D | quic-api.md | 33 - [`SSL_handle_events`](#-ssl-handle-events-)
346 network I/O processing as the resources needed to handle the connection are
1453 in generation of a further `CONNECTION_CLOSE` frame. This is necessary to handle
1480 There are only really two ways to handle this:
|
| /openssl/doc/man7/ |
| H A D | ossl-guide-quic-multi-stream.pod | 89 the peer has initiated that are waiting for the application to handle. An
154 L<SSL_get_certificate(3)> can be used to obtain a handle on the peer certificate
|
| H A D | provider-decoder.pod | 207 can handle.
|
| H A D | provider-kdf.pod | 140 can handle, respectively. OSSL_FUNC_kdf_gettable_ctx_params() and
|
| H A D | provider-rand.pod | 174 can handle, respectively. OSSL_FUNC_rand_gettable_ctx_params()
|
| H A D | openssl-quic.pod | 675 QUIC implementation of whether it is prepared to handle local and/or peer
730 network BIO. This is typically an OS socket handle, though custom BIOs could
|
| /openssl/doc/man1/ |
| H A D | openssl-pkcs8.pod.in | 36 This command processes private keys in PKCS#8 format. It can handle
|
| H A D | openssl-ca.pod.in | 450 that some software (for example Netscape) can't handle V2 CRLs. See
781 replacement could handle things properly. The script
|
| H A D | openssl-pkeyutl.pod.in | 317 When disabled, it's the callers' responsibility to handle the returned
|
| /openssl/include/openssl/ |
| H A D | asn1.h.in | 338 * To handle both cases transparently the macros below
366 * Platforms that can't easily handle shared global variables are declared as
|
| /openssl/doc/internal/man3/ |
| H A D | OPTIONS.pod | 305 and common code to handle them. The categories are identified by a
|
| /openssl/crypto/engine/ |
| H A D | README.md | 78 the RSA_METHOD would call ENGINE_get_RSA() each time on its ENGINE handle to
|
Completed in 58 milliseconds
1234567
