Home
last modified time | relevance | path

Searched refs:send (Results 1 – 25 of 104) sorted by relevance

12345

/openssl/external/perl/Text-Template-1.56/
H A DINSTALL10 to test the package. If it fails any tests, please send me the output
29 If you have problems, send me mail:
/openssl/include/internal/
H A Dsockets.h178 # define writesocket(s,b,n) send((s),(b),(n),0)
182 # define writesocket(s,b,n) send(s,b,n,0)
187 # define writesocket(s,b,n) send((s),(b),(n),0)
H A Dstatem.h157 void ossl_statem_check_finish_init(SSL_CONNECTION *s, int send);
/openssl/doc/designs/quic-design/
H A Dquic-connID-retire.md46 * Not sure if it is mandatory to send a retirement.
66 * retired routes where we've outstanding data to send will have that data
67 sent before the retirement acks are send. If these fragments need to
H A Dquic-tls.md65 * Called to send data on the crypto stream. We use a callback rather than
113 * Transport parameters which client should send. Buffer lifetime must
129 In the event that an error occurs a normal TLS handshake would send a TLS alert
131 attempts to send an alert and will communicate this via the `alert_cb` callback.
133 QUIC requires the use of a TLS extension in order to send and receive "transport
194 Invoked every time the TLS implementation wants to send TLS handshake data. This
196 special processing in the event that the TLS implementation wants to send an
H A Dquic-fc.md26 have not, as the peer may wait indefinitely for us to send more data before
37 example, a peer is not allowed to wait until we send `DATA_BLOCKED` to increase
118 The On TX event is passed to the state machine whenever we send a packet.
130 number of controlled bytes we are allowed to send since the start of the
137 number of controlled bytes we are allowed to send). This value is reduced by the
169 Note that the number of controlled bytes we can send in a stream is limited by
171 bytes we can send is the lesser value of the values returned by the Get TX
H A Dtx-packetiser.md108 instance (for streams with a send part). Streams are marked inactive when
126 To send accumulated frames as packets to the QUIC Write Record Layer:
133 It will also attempt to create multiple packets to send simultaneously.
171 allowed to send in a packet.
188 and callers may send them by direct calls to the record layer.
387 need to send it if
444 have any `STREAM` frame to send at all, it cancels any need for any `PING`
510 - **Intrapacket muxing (IRPM)**. When the data available to send across all
633 encryption levels (ELs). The TX packetiser decides what EL to use to send a
657 to send.
[all …]
H A Dconnection-id-cache.md83 IDs covered from our cache and then send back an acknowledgement of
86 If we want to retire a frame, we send a retirement frame and mark the
87 IDs covered in our cache as _retired_. This means that we cannot send
/openssl/doc/man3/
H A DSSL_get_peer_certificate.pod29 Due to the protocol definition, a TLS/SSL server will always send a
30 certificate, if present. A client will only send a certificate when
H A DSSL_stream_conclude.pod15 SSL_stream_conclude() signals the normal end-of-stream condition for the send
27 unaffected, and the peer may continue to send data until it also signals the end
H A DSSL_CTX_set_client_cert_cb.pod44 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
H A DSSL_CTX_set_session_ticket_cb.pod84 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
H A DBIO_sendmmsg.pod7 BIO_err_is_non_fatal - send and receive multiple datagrams in a single call
34 BIO_sendmmsg() and BIO_recvmmsg() functions can be used to send and receive
46 the data to send, or to be filled with a received message. I<data_len> should be
63 When these functions are used to send and receive datagrams, the I<peer> field
98 I<num_msg> should be sent to the maximum number of messages to send or receive,
H A DBIO_s_null.pod27 data by writing through a digest bio but not send the digested data anywhere.
H A DSSL_alert_type_string.pod42 (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
H A DSSL_CTX_set_verify.pod88 B<Server mode:> the server will not send a client certificate request to the
89 client, so the client will not send a certificate.
92 server will send a certificate which will be checked. The result of the
134 B<Server mode:> the server will not send a client certificate request
135 during the initial handshake, but will send the request via
H A DSSL_shutdown.pod73 process and causes OpenSSL to try to send a close_notify shutdown alert to the
135 attempt is made to send a close_notify alert, regardless of whether the attempt
149 that the peer will not send more data, otherwise there is a risk of an
151 process, in which both parties send close_notify alerts and SSL_shutdown()
187 There are SSL/TLS implementations that never send the required close_notify
292 pending send buffers flushed in this manner.
296 SSL_shutdown_ex(); in this case, data remaining in stream send buffers may not
H A DSSL_get_session.pod31 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
H A DSSL_read_early_data.pod58 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
299 if a client does not send any early data.
H A DSSL_CTX_set_session_cache_mode.pod28 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
H A DSSL_get_error.pod30 Some TLS implementations do not send a close_notify alert on shutdown.
78 operation was a write to a nonblocking B<BIO> and it was unable to send all data
93 B<SSL_ERROR_WANT_WRITE> indicates that the OpenSSL internal send buffer for a
H A DSSL_write.pod52 relevant QUIC stream's send part is concluded automatically as though
62 Setting this flag does not cause a stream's send part to be concluded if not all
130 SSL_write_ex() can be called with num=0, but will not send application data to
/openssl/doc/man7/
H A Dossl-guide-quic-multi-stream.pod33 normally you would have at least one). A stream is used to send and receive
110 object if a default stream is in use) then you can send and receive data over it
120 that the peer will send no more data on that stream. Note that the
126 received on it, however an application can still send data to the peer until
127 the send side of the stream has also been concluded. This can happen by the
129 send more data on a stream after L<SSL_stream_conclude(3)> has been called.
161 a simple multi-stream QUIC client application which connects to a server, send
197 For the purposes of this example we will create two different streams to send
217 avoid repeating too much code we write a simple helper function to send an HTTP
237 appropriate HTTP requests. We can then call our helper function above to send
[all …]
/openssl/demos/sslecho/
H A DREADME.md11 was added to open a connection with the server and to send keyboard input
/openssl/test/
H A DREADME.ssltest.md48 * 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.

Completed in 61 milliseconds

12345