/openssl-master/doc/man3/ |
A D | SSL_shutdown.pod | 18 SSL_shutdown() tries to send the close_notify shutdown alert to the peer. 31 It is acceptable for an application to only send its shutdown alert and 74 state but not actually send the close_notify alert messages, 83 There are implementations that do not send the required close_notify alert. 93 When the application is the first party to send the close_notify 94 alert, SSL_shutdown() will only send the alert and then set the 103 to send back a close_notify alert. 107 The peer is still allowed to send data after receiving the close_notify 109 When it is done sending data, it will send the close_notify alert. 121 SSL_shutdown() will send the close_notify alert, set the SSL_SENT_SHUTDOWN [all …]
|
A D | SSL_get_peer_certificate.pod | 24 Due to the protocol definition, a TLS/SSL server will always send a 25 certificate, if present. A client will only send a certificate when
|
A D | SSL_CTX_set_client_cert_cb.pod | 44 did send the request. 62 If the callback returns no certificate, the OpenSSL library will not send 76 longer chain, the client must send the complete chain (with the option
|
A D | SSL_CTX_set_session_ticket_cb.pod | 84 valid for a client to send an empty ticket. 109 policy. Note that in TLSv1.3 a client may send more than one ticket in a single 115 Do not use a ticket (if one was available). Do not send a renewed ticket to the 128 Use the ticket. Do not send a renewed ticket to the client. It is an error for
|
A D | BIO_s_null.pod | 27 data by writing through a digest bio but not send the digested data anywhere.
|
A D | SSL_CTX_set_verify.pod | 73 B<Server mode:> the server will not send a client certificate request to the 74 client, so the client will not send a certificate. 77 server will send a certificate which will be checked. The result of the 119 B<Server mode:> the server will not send a client certificate request 120 during the initial handshake, but will send the request via
|
A D | SSL_alert_type_string.pod | 42 (The sending party may however decide to send a fatal error.) The 101 A client, that was asked to send a certificate, does not send a certificate
|
A D | SSL_get_session.pod | 31 main handshake has occurred. The server will send the session information to the 39 Additionally, in TLSv1.3, a server can send multiple messages that establish a
|
A D | OSSL_HTTP_REQ_CTX.pod | 63 which gets populated with the B<BIO> to write/send the request to (I<wbio>), 129 OSSL_HTTP_REQ_CTX_nbio() attempts to send the request prepared in I<rctx> 176 to send further requests and OSSL_HTTP_is_alive() returns nonzero, 180 I/O error when trying to send the next request via I<rctx>.
|
A D | SSL_read_early_data.pod | 58 These functions are used to send and receive early data where TLSv1.3 has been 64 to send data from the server to the client when the client has not yet completed 84 determine if a session established with a server can be used to send early data. 94 A client uses the function SSL_write_early_data() to send early data. This 114 When the client no longer wishes to send any more early data then it should 294 if a client does not send any early data.
|
A D | SSL_CTX_set_session_cache_mode.pod | 28 In order to reuse a session, a client must send the session's id to the 29 server. It can only send exactly one id. The server then either
|
A D | SSL_CTX_set_quiet_shutdown.pod | 35 Normally when a SSL connection is finished, the parties must send out
|
A D | SSL_set_shutdown.pod | 50 (according to the TLS RFC, it is acceptable to only send the close_notify
|
A D | SSL_get_peer_cert_chain.pod | 36 If the session is resumed peers do not send certificates so a NULL pointer
|
A D | DTLSv1_listen.pod | 30 address. An attacker could forge its source IP address and then send handshake 31 initiation messages to the server. The server would then send its response to
|
A D | SSL_CTX_set_max_cert_list.pod | 34 During the handshake process, the peer may send a certificate chain.
|
/openssl-master/ssl/record/ |
A D | record.h | 222 __owur int ssl3_enc(SSL *s, SSL3_RECORD *inrecs, size_t n_recs, int send, 224 __owur int n_ssl3_mac(SSL *ssl, SSL3_RECORD *rec, unsigned char *md, int send); 229 __owur int tls1_mac(SSL *ssl, SSL3_RECORD *rec, unsigned char *md, int send); 230 __owur int tls13_enc(SSL *s, SSL3_RECORD *recs, size_t n_recs, int send,
|
A D | record_local.h | 127 int early_data_count_ok(SSL *s, size_t length, size_t overhead, int send);
|
/openssl-master/external/perl/Text-Template-1.56/ |
A D | INSTALL | 10 to test the package. If it fails any tests, please send me the output 29 If you have problems, send me mail:
|
/openssl-master/include/internal/ |
A D | sockets.h | 133 # define writesocket(s,b,n) send((s),(b),(n),0) 139 # define writesocket(s,b,n) send(s,b,n,0) 144 # define writesocket(s,b,n) send((s),(b),(n),0)
|
/openssl-master/ssl/statem/ |
A D | statem.h | 150 void ossl_statem_check_finish_init(SSL *s, int send);
|
/openssl-master/test/ |
A D | README.ssltest.md | 48 * ApplicationData - amount of application data bytes to send (integer, defaults 53 * MaxFragmentSize - maximum send fragment size (integer, defaults to 512 in 107 send. If this is "empty" the list is expected to be empty otherwise it 110 * ExpectedServerCANames - list of CA names the client must send, TLS 1.3 only.
|
/openssl-master/doc/man1/ |
A D | openssl-s_server.pod.in | 201 client does not have to send one, with the B<-Verify> option the client 322 File to send output of B<-msg> or B<-trace> to, default standard output. 436 Some TLS implementations do not send the mandatory close_notify alert on 439 option is enabled the peer does not need to send the close_notify alert and a 449 On servername mismatch send fatal alert (default: warning alert). 566 The maximum size of data fragment to send. 691 Expect the client to send PSK identity I<val> when using a PSK 775 instead of BIO_write() to send the HTTP response requested by a client.
|
A D | openssl-passphrase-options.pod | 58 send the data via a pipe for example.
|
A D | openssl-s_client.pod.in | 447 Enable send/receive timeout on DTLS connections. 473 File to send output of B<-msg> or B<-trace> to, default standard output. 552 The maximum size of data fragment to send. 580 Some TLS implementations do not send the mandatory close_notify alert on 583 option is enabled the peer does not need to send the close_notify alert and a 735 Reads the contents of the specified file and attempts to send it as early data 741 For TLSv1.3 only, send the Post-Handshake Authentication extension. This will 864 is necessary to use the B<-prexit> option and send an HTTP request
|