/openssl/doc/man3/ |
H A D | SSL_free.pod | 17 reference count has reached 0. 29 The ssl session has reference counts from two users: the SSL object, for 45 If the stream has a sending part (in other words, if it is bidirectional or a 46 locally-initiated unidirectional stream) and that part has not been concluded 54 If the stream has a receiving part (in other words, if it is bidirectional or a 55 remotely-initiated unidirectional stream), and the peer has not yet concluded
|
H A D | BIO_connect.pod | 34 BIO_listen() has B<sock> start listening on the address and service 95 (-1) on error. When an error has occurred, the OpenSSL error stack 96 will hold the error data and errno has the system error. 99 When an error has occurred, the OpenSSL error stack will hold the error 100 data and errno has the system error. 103 B<INVALID_SOCKET> (-1) on error. When an error has occurred, the 104 OpenSSL error stack will hold the error data and errno has the system
|
H A D | SSL_read_early_data.pod | 58 These functions are used to send and receive early data where TLSv1.3 has been 61 Early data can be sent if a session has previously been established with the 67 Early data has weaker security properties than other data sent over an SSL/TLS 75 done before the full handshake has been completed. Specifically the client's 80 A server or client can determine whether the full handshake has been completed 120 A server may choose to ignore early data that has been sent to it. Once the 128 connection for which early data has been enabled using 173 L<SSL_write(3)> until SSL_read_early_data() has returned with 174 SSL_READ_EARLY_DATA_FINISH. Once it has done so the connection to the client 179 attempt to complete the connection before SSL_read_early_data() has returned [all …]
|
H A D | SSL_shutdown.pod | 41 completed. Once the shutdown process has completed, subsequent calls to 199 when all data has been received. 203 which indicates unambiguously when all data has been sent. 298 condition has occurred and the delivery of data written to streams via 357 either success or failure depending on whether a shutdown has occurred. 359 If a locally initiated shutdown has already been triggered or the connection has 360 started terminating for another reason, this flag has no effect. 382 The shutdown process is ongoing and has not yet completed. 385 peer has not yet replied in turn with its own close_notify. 388 sent but the connection closure process has not yet completed. [all …]
|
H A D | SSL_CTX_set_info_callback.pod | 63 Callback has been called to indicate state change or some other significant 69 Callback has been called to indicate exit of a handshake function. This will 75 Callback has been called during read operation. 79 Callback has been called during write operation. 83 Callback has been called due to an alert being sent or received. 99 Callback has been called because a new handshake is started. It also occurs when 104 Callback has been called because a handshake is finished. It also occurs if the
|
H A D | SSL_get_error.pod | 52 The TLS/SSL peer has closed the connection for writing by sending the 56 indicate that the underlying transport has been closed. 69 If at a later time the underlying B<BIO> has data available for reading the same 94 given QUIC stream has been filled. Likewise, B<SSL_ERROR_WANT_READ> indicates 125 In order to find out, when the connection has been successfully established, 132 SSL_CTX_set_client_cert_cb() has asked to be called again. 141 engine is being used. An application can determine whether the engine has 152 mode has been set to SSL_MODE_ASYNC using L<SSL_CTX_set_mode(3)> or 153 L<SSL_set_mode(3)> and a maximum limit has been set on the async job pool 156 thread has completed. [all …]
|
H A D | SSL_CTX_set_tlsext_servername_callback.pod | 40 This is used to indicate that the servername requested by the client has been 57 warning alerts, so if TLSv1.3 has been negotiated then this return value is 79 If a servername has been set via a call to SSL_set_tlsext_host_name() then it 82 If one has not been set, but a TLSv1.2 resumption is being attempted and the 107 =item On the server, after the servername extension has been processed and a 113 =item On the server, after the servername extension has been processed and a 156 corner cases. This has been fixed from OpenSSL 1.1.1e. 161 the client it returned the servername from the second handshake. This has now 167 servername requested in the original handshake. This has now been changed to
|
H A D | SSL_CTX_use_psk_identity_hint.pod | 80 or SSL_set_psk_find_session_callback() for this purpose instead. If TLSv1.3 has 81 been negotiated then OpenSSL will first check to see if a callback has been set 84 check to see if a callback has been set via SSL_CTX_set_psk_server_callback() or 91 has occurred so that L<SSL_session_reused(3)> will return true. 110 PSK identity was found and the server callback has provided the PSK 129 below) and TLSv1.3. However, the RFC has this note of caution: 132 in both versions, only limited analysis has been done. Implementations can
|
H A D | SSL_key_update.pod | 34 SSL_key_update() must only be called after the initial handshake has been 35 completed and TLSv1.3 or QUIC has been negotiated, at the same time, the 36 application needs to ensure that the writing of data has been completed. The key 42 operation has been scheduled but not yet performed. The type of the pending key 78 renegotiation request has been scheduled but not yet acted on, or 0 otherwise. 86 B<SSL_KEY_UPDATE_NOT_REQUESTED> as B<updatetype> has the same effect as passing 106 has been scheduled but not yet acted on, or 0 otherwise.
|
H A D | SSL_connect.pod | 24 handshake has been finished or an error occurred. 39 buffer outgoing TCP data if a TCP packet has already been sent for which no 40 corresponding ACK has been received yet from the peer. This can have performance 44 typical for many protocols) then this data could be buffered until an ACK has 67 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
|
H A D | SSL_in_init.pod | 31 SSL_in_before() returns 1 if no SSL/TLS handshake has yet been initiated, or 0 64 B<message> is the name of a handshake message that is being or has been sent, or 65 is being or has been processed. 78 Handshake message sending/processing has completed.
|
H A D | SSL_CTX_set_session_ticket_cb.pod | 42 decryption has been attempted and any session ticket application data is 63 after a session has been created. The B<dec_cb> is provided to notify the 64 application that a session ticket has just been decrypted. 68 When the B<dec_cb> callback is invoked, the SSL_SESSION B<ss> has not yet been 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 146 If B<status> has the value B<SSL_TICKET_EMPTY> or B<SSL_TICKET_NO_DECRYPT> then 148 argument. If B<status> has the value B<SSL_TICKET_SUCCESS> or
|
H A D | DSA_generate_parameters.pod | 67 When a candidate for q has passed a test by trial division, 76 When a prime q has been found, B<BN_GENCB_call(cb, 2, 0)> and 86 When a candidate for p has passed the test by trial division, 95 When p has been found, B<BN_GENCB_call(cb, 2, 1)> is called. 99 When the generator has been found, B<BN_GENCB_call(cb, 3, 1)> is called.
|
H A D | SSL_poll.pod | 97 If a B<SSL_POLL_ITEM> has a poll descriptor type of 156 permanent exception condition; as such, after an event has been reported by 160 repeated notifications and has not caused the underlying readiness condition 202 Error at connection level. This event is raised when a connection has failed. 209 Error at connection level (drained). This event is raised when a connection has 210 finished terminating, and has reached the terminated state. This event will 219 stream has a read part and that read part has been reset by the peer (for 225 stream has a write part and that write part has been reset by the peer using a 231 connection SSL object with a default stream attached) has application data 246 This event is never raised by a stream which has had its send part concluded [all …]
|
H A D | SSL_CTX_has_client_custom_ext.pod | 16 SSL_CTX_has_client_custom_ext() checks whether a handler has been set for a 21 Returns 1 if a handler has been set, 0 otherwise.
|
H A D | DSA_get0_pqg.pod | 54 after this function has been called. 59 been set yet, although if the private key has been set then the public key must 68 object, and therefore they should not be freed directly after this function has 83 DSA_get0_engine() returns a handle to the ENGINE that has been set for this DSA 84 object, or NULL if no such ENGINE has been set. 100 has been set.
|
H A D | SSL_SESSION_get_compress_id.pod | 16 If compression has been negotiated for an ssl session then 18 0 otherwise. The only built-in supported compression method is zlib which has an
|
H A D | SSL_get_certificate.pod | 28 If it is called before certificate selection has occurred, it returns the most 29 recently added certificate, or NULL if no certificate has been added. 33 After certificate selection has occurred, it returns the certificate which was
|
H A D | X509_get_version.pod | 34 version. So B<X509_VERSION_3> has value 2 and B<X509_VERSION_1> has value 0. 48 The version field of certificates, certificate requests and CRLs has a
|
H A D | SSL_CTX_set_tlsext_status_cb.pod | 60 the client has previously called SSL_set_tlsext_status_type(). It will return 61 B<TLSEXT_STATUSTYPE_ocsp> if it has been called or -1 otherwise. On the server 70 call to the d2i_OCSP_RESPONSE() function. If the server has not provided any 90 SSL_TLSEXT_ERR_OK (meaning that the OCSP response that has been set should be 92 returned) or SSL_TLSEXT_ERR_ALERT_FATAL (meaning that a fatal error has
|
/openssl/include/internal/ |
H A D | safe_math.h | 18 # define has(func) __has_builtin(func) macro 20 # define has(func) 1 macro 24 # ifndef has 25 # define has(func) 0 macro 31 # if has(__builtin_add_overflow) 87 # if has(__builtin_sub_overflow) 131 # if has(__builtin_mul_overflow)
|
/openssl/doc/man7/ |
H A D | ossl-guide-quic-client-non-block.pod | 28 nonblocking socket. However, despite this, the B<SSL> object still has blocking 29 behaviour. When the B<SSL> object has blocking behaviour then this means that 41 has nonblocking behaviour. With a nonblocking B<SSL> object, functions such as 55 the application has to do, it must also be prepared to come back and retry the 57 complete. Ideally it would only do this in the event that something has changed 98 * whether the state of the underlying socket has changed or not. 172 stream but no data has not yet arrived from the peer for that stream). 179 out what type of error has occurred. If the error is non-fatal and can be 194 the stream has been reset by the peer, or because the underlying connection has 202 connection has closed. [all …]
|
H A D | ossl-guide-tls-introduction.pod | 41 the protocol has undergone various changes over the years. Consequently there 70 OpenSSL will always try to negotiate the highest protocol version that it has 96 certificate if it has been able to confirm that the server operator does indeed 98 operator has control of the private key. 100 In this way, if the client trusts the CA that has signed the server's 114 That intermediate CA also has a certificate containing its public key which is 187 SSL handshake has read 4584 bytes and written 403 bytes 193 SSL handshake has read 4584 bytes and written 403 bytes 208 application. Once a connection with a remote peer has been established an 247 B<SSL_CTX> (if one has not already been created) and configures it. [all …]
|
/openssl/test/ssl-tests/ |
H A D | 06-sni-ticket.cnf.in | 61 # If the client has session tickets disabled, then No support 62 # If the server initial_ctx has session tickets disabled, then No support 63 # If SNI is in use, then if the "switched-to" context has session tickets disabled,
|
/openssl/external/perl/Text-Template-1.56/ |
H A D | README | 6 has little Perl programs embedded in it here and there. When you 14 It has come to our attention that you are delinquent in your 29 It has come to our attention that you are delinquent in your
|