Home
last modified time | relevance | path

Searched refs:SSL_write (Results 1 – 25 of 54) sorted by relevance

123

/openssl/doc/man3/
H A DSSL_set_default_stream_mode.pod23 stream is a QUIC stream to which calls to L<SSL_read(3)> and L<SSL_write(3)>
29 connection once L<SSL_read(3)> or L<SSL_write(3)> is called.
35 L<SSL_write(3)>) after establishing a connection, OpenSSL will wait for the
37 default stream. Conversely, if L<SSL_write(3)> is called before any call to
49 L<SSL_read(3)> and L<SSL_write(3)>) will fail.
65 This is the default setting. If L<SSL_write(3)> is called prior to any call to
68 L<SSL_write(3)>, OpenSSL waits for an incoming stream from the peer (causing
78 In this mode, if L<SSL_write(3)> is called prior to any call to L<SSL_read(3)>,
82 called prior to any call to L<SSL_write(3)> is unchanged.
87 L<SSL_read(3)> and L<SSL_write(3)> calls cannot be made on the QUIC connection
H A DSSL_CTX_set_mode.pod43 SSL_write(). When not set (the default), SSL_write_ex() or SSL_write() will only
45 SSL_write() returns successful, B<r> bytes have been written and the next call
46 to SSL_write_ex() or SSL_write() must only send the n-r bytes left, imitating
54 Make it possible to retry SSL_write_ex() or SSL_write() with changed buffer
56 avoid the misconception that nonblocking SSL_write() behaves like
135 L<SSL_write(3)>, L<SSL_get_error(3)>
H A DSSL_stream_conclude.pod19 Any data already queued for transmission via a call to SSL_write() will still be
23 the stream via calls to SSL_write(). Further attempts to call SSL_write() after
H A DSSL_write.pod5 SSL_write_ex2, SSL_write_ex, SSL_write, SSL_sendfile, SSL_WRITE_FLAG_CONCLUDE -
19 int SSL_write(SSL *ssl, const void *buf, int num);
23 SSL_write_ex() and SSL_write() write B<num> bytes from the buffer B<buf> into
75 SSL_write_ex(), or SSL_write().
112 When used with a QUIC SSL object, calling an I/O function such as SSL_write()
116 SSL_write() is called regularly, or alternatively ensure that SSL_handle_events()
129 You should not call SSL_write() with num=0, it will return an error.
147 For SSL_write() the following return values can occur:
H A DSSL_get_error.pod18 SSL_write_ex() or SSL_write() on B<ssl>. The value returned by that TLS/SSL I/O
98 even when the call that set this error was an SSL_write() or SSL_write_ex().
99 However, if the call was an SSL_write() or SSL_write_ex(), it should be called
101 from SSL_write() or SSL_write_ex() then you should not do any other operation
102 that could trigger B<IO> other than to repeat the previous SSL_write() call.
112 and SSL_write() or SSL_write_ex() may want to read data.
116 SSL_peek(), SSL_write_ex(), and SSL_write() will handle any pending handshakes.
H A DSSL_get_stream_read_state.pod65 L<SSL_write(3)> calls will not succeed.
80 using L<SSL_free(3)>. Calls to L<SSL_write(3)> will fail.
98 Calls to L<SSL_write(3)> will fail.
109 read via L<SSL_read(3)> when this state is returned. Calls to L<SSL_write(3)>
H A DSSL_CTX_set_split_send_fragment.pod67 amount of data provided to the SSL_write_ex() or SSL_write() call divided by
73 SSL_write/SSL_write_ex called with 0-2000 bytes == 1 pipeline used
75 SSL_write/SSL_write_ex called with 2001-4000 bytes == 2 pipelines used
77 SSL_write/SSL_write_ex called with 4001-6000 bytes == 3 pipelines used
79 SSL_write/SSL_write_ex called with 6001+ bytes == 4 pipelines used
H A DSSL_set_connect_state.pod43 using L<SSL_write_ex(3)>, L<SSL_write(3)>, L<SSL_read_ex(3)>, or L<SSL_read(3)>,
64 L<SSL_write_ex(3)>, L<SSL_write(3)>, L<SSL_read_ex(3)>, L<SSL_read(3)>,
H A DSSL_stream_reset.pod32 does not guarantee that any data already passed to L<SSL_write(3)> will be
33 received by the peer, and data already passed to L<SSL_write(3)> but not yet
H A DSSL_new_stream.pod35 normal way using L<SSL_read(3)> and L<SSL_write(3)>.
58 by calling L<SSL_write(3)>. However, no actual stream data (or QUIC frames
H A DSSL_handle_events.pod43 L<SSL_write(3)>. Note that this is different to QUIC which also performs event
62 is not necessary unless no I/O calls (such as L<SSL_read(3)> or L<SSL_write(3)>)
/openssl/doc/designs/quic-design/
H A Derror-handling.md51 Operations on QUIC streams (SSL_write(), SSL_read()) can also trigger errors,
54 they are left on the error stack of the thread that called SSL_write()
67 processing, or when calling SSL_read()/SSL_write() on a stream need to be
68 replicated for SSL_read()/SSL_write() calls on other streams.
78 When returning to an application from an SSL_read()/SSL_write() call with
100 are calling SSL_read()/SSL_write() simultaneously they all get
H A Dquic-api.md21 - [`SSL_write`, `SSL_write_ex`](#-ssl-write----ssl-write-ex-)
237 #### `SSL_write`, `SSL_write_ex`
339 via `SSL_stream_conclude`), data appended to the stream via `SSL_write` will
410 non-partial-write `SSL_write` operation spanning multiple `SSL_write` calls,
581 flag, in which case any data appended to streams via `SSL_write` (or any
584 data written to streams via `SSL_write` is no longer relevant. Application
666 the stream via calls to `SSL_write`. Further attempts to call `SSL_write` after
751 * and that future calls to SSL_write will fail.
1148 * unidirectional, calls to `SSL_write` will fail. Attempts to create
1155 * local application calls `SSL_write` prior to the peer creating a
[all …]
H A Dquic-requirements.md125 * Simple clients that just do basic SSL_read/SSL_write or BIO_read/BIO_write
129 * Simple servers that just do basic SSL_read/SSL_write or BIO_read/BIO_write
200 * Support simple clients that just do basic SSL_read/SSL_write or BIO_read/BIO_write
/openssl/test/
H A Dquic_newcid_test.c77 if (!TEST_int_eq(SSL_write(cssl, msg, msglen), msglen)) in test_ncid_frame()
124 if (!TEST_int_eq(SSL_write(cssl, msg, msglen), msglen)) in test_ncid_frame()
H A Dfatalerrtest.c72 if (!TEST_int_le(SSL_write(sssl, msg, strlen(msg)), 0)) in test_fatalerr()
H A Dquic_client_test.c120 if (!TEST_int_eq(SSL_write(c_ssl, msg1, sizeof(msg1) - 1), in test_quic_client_ex()
H A Ddtls_mtu_test.c104 if (!TEST_int_eq(SSL_write(clnt_ssl, buf, s), (int)s)) in mtu_test()
H A Dsslcorrupttest.c231 if (!TEST_int_ge(SSL_write(client, junk, sizeof(junk)), 0)) in test_ssl_corrupt()
/openssl/demos/sslecho/
H A Dmain.c257 if (SSL_write(ssl, rxbuf, rxlen) <= 0) { in main()
327 if ((result = SSL_write(ssl, txbuf, strlen(txbuf))) <= 0) { in main()
H A DREADME.md20 SSL_write() and SSL_read().
/openssl/apps/
H A Ds_time.c285 if (buf_len <= 0 || SSL_write(scon, buf, buf_len) <= 0) in s_time_main()
338 if (buf_len <= 0 || SSL_write(scon, buf, buf_len) <= 0) in s_time_main()
366 if (buf_len <= 0 || SSL_write(scon, buf, buf_len) <= 0) in s_time_main()
/openssl/doc/man7/
H A Dopenssl-quic.pod24 L<SSL_write(3)> on the QUIC connection SSL object read and write from that
26 perspective depends on whether L<SSL_read(3)> or L<SSL_write(3)> is called
71 connection SSL object; L<SSL_read(3)> and L<SSL_write(3)> calls to the QUIC
81 L<SSL_write(3)> on the connection, it is assumed that the application protocol
85 application calls L<SSL_write(3)> before any call to L<SSL_read(3)> on the
111 receiving application data using L<SSL_read(3)> and L<SSL_write(3)>.
121 such as L<SSL_write(3)> or L<SSL_get_stream_id(3)> will fail.
183 I/O functions such as L<SSL_read(3)> and L<SSL_write(3)>, but the underlying
505 L<SSL_write(3)>), if ever.
516 functions on an SSL object, such as L<SSL_read(3)> and L<SSL_write(3)>
[all …]
/openssl/doc/designs/ddd/
H A Dddd-03-fd-blocking.c96 return SSL_write(ssl, buf, buf_len); in tx()
/openssl/fuzz/
H A Dquic-client.c172 ret = SSL_write(stream, tmp, writelen); in FuzzerTestOneInput()

Completed in 74 milliseconds

123