Home
last modified time | relevance | path

Searched refs:SSL_read_ex (Results 1 – 14 of 14) sorted by relevance

/freebsd-12-stable/crypto/openssl/doc/man3/
DSSL_read.pod5 SSL_read_ex, SSL_read, SSL_peek_ex, SSL_peek
12 int SSL_read_ex(SSL *ssl, void *buf, size_t num, size_t *readbytes);
20 SSL_read_ex() and SSL_read() try to read B<num> bytes from the specified B<ssl>
21 into the buffer B<buf>. On success SSL_read_ex() will store the number of bytes
24 SSL_peek_ex() and SSL_peek() are identical to SSL_read_ex() and SSL_read()
26 the read, so that a subsequent call to SSL_read_ex() or SSL_read() will yield
31 In the paragraphs below a "read function" is defined as one of SSL_read_ex(),
98 SSL_read_ex() and SSL_peek_ex() will return 1 for success or 0 for failure.
141 The SSL_read_ex() and SSL_peek_ex() functions were added in OpenSSL 1.1.1.
DSSL_pending.pod19 read by the application via a call to L<SSL_read_ex(3)> or L<SSL_read(3)>.
37 return 1, and then a subsequent call to SSL_read_ex() or SSL_read() to return no
41 SSL_read_ex() or SSL_read() call because the buffered and unprocessed data is
53 L<SSL_read_ex(3)>, L<SSL_read(3)>, L<SSL_CTX_set_read_ahead(3)>,
DSSL_get_error.pod17 SSL_read_ex(), SSL_read(), SSL_peek_ex(), SSL_peek(), SSL_shutdown(),
58 SSL_read() and SSL_read_ex() can also set B<SSL_ERROR_WANT_READ> when there is
73 It is safe to call SSL_read() or SSL_read_ex() when more data is available
85 SSL_read_ex(), SSL_read(), SSL_peek_ex(), or SSL_peek() may want to write data
89 either the client or the server); SSL_read_ex(), SSL_read(), SSL_peek_ex(),
DSSL_read_early_data.pod103 L<SSL_write_ex(3)>, L<SSL_read_ex(3)>, L<SSL_connect(3)>, L<SSL_do_handshake(3)>
108 calls to L<SSL_read_ex(3)> and L<SSL_read(3)> with calls to
132 L<SSL_write_ex(3)>, L<SSL_read_ex(3)>, L<SSL_accept(3)>, L<SSL_do_handshake(3)>,
135 SSL_read_early_data() is similar to L<SSL_read_ex(3)> with the following
136 differences. Refer to L<SSL_read_ex(3)> for full details.
145 same way as a 0 return value from L<SSL_read_ex(3)>.
150 the same way as a 1 return value from L<SSL_read_ex(3)>. You should continue to
172 Servers must not call L<SSL_read_ex(3)>, L<SSL_read(3)>, L<SSL_write_ex(3)> or
177 standard read function such as L<SSL_read_ex(3)>, which will transparently
355 L<SSL_read_ex(3)>,
DSSL_key_update.pod36 until the next time an IO operation such as SSL_read_ex() or SSL_write_ex()
51 such as SSL_read_ex() or SSL_write_ex() takes place on the connection a check
92 L<ssl(7)>, L<SSL_read_ex(3)>,
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)>,
DSSL_CTX_set_mode.pod61 L<SSL_read_ex(3)> and L<SSL_read(3)> can return with a failure and indicate the
81 Otherwise the call to SSL_read() or SSL_read_ex() might hang when a
131 L<ssl(7)>, L<SSL_read_ex(3)>, L<SSL_read(3)>, L<SSL_write_ex(3)> or
DSSL_write.pod109 L<SSL_get_error(3)>, L<SSL_read_ex(3)>, L<SSL_read(3)>
/freebsd-12-stable/secure/lib/libssl/
DVersion.map491 SSL_read_ex;
/freebsd-12-stable/crypto/openssl/doc/man7/
Dssl.pod31 L<SSL_read_ex(3)>, L<SSL_read(3)>, L<SSL_write_ex(3)> and L<SSL_write(3)> are
804 L<SSL_read_ex(3)>,
/freebsd-12-stable/crypto/openssl/ssl/
Dssl_lib.c1811 int SSL_read_ex(SSL *s, void *buf, size_t num, size_t *readbytes) in SSL_read_ex() function
1851 ret = SSL_read_ex(s, buf, num, readbytes); in SSL_read_early_data()
/freebsd-12-stable/crypto/openssl/include/openssl/
Dssl.h1840 __owur int SSL_read_ex(SSL *ssl, void *buf, size_t num, size_t *readbytes);
/freebsd-12-stable/crypto/openssl/crypto/err/
Dopenssl.txt1317 SSL_F_SSL_READ_EX:434:SSL_read_ex
/freebsd-12-stable/secure/lib/libcrypto/man/man3/
DMakefile2820 MLINKS+= SSL_read.3 SSL_read_ex.3