Home
last modified time | relevance | path

Searched refs:read (Results 1 – 25 of 222) sorted by relevance

123456789

/openssl/doc/man3/
H A DSSL_read.pod6 - read bytes from a TLS/SSL connection
22 actually read in B<*readbytes>.
37 the read function operation. The behaviour of the read functions depends on the
43 invocation of a read function.
49 buffered inside the SSL layer and will be retrieved on the next read
69 read operation has been finished or an error occurred, except when a
79 return value of the read function will yield B<SSL_ERROR_WANT_READ> or
82 a read function can also cause write operations.
84 to satisfy the needs of the read function.
109 Failure means that no bytes could be read from the SSL connection.
[all …]
H A DBIO_s_mem.pod37 subsequent call to L<BIO_read(3)> will read the data in that datagram. The
52 Unless the memory BIO is read only any data read from it is deleted from
67 data can be read again. On a read only BIO it similarly restores the BIO to
68 its original state and the read only data can be read again.
113 Every write after partial read (not all data in the memory buffer was read)
122 Switching a memory BIO from read write to read only is not supported and
125 immediately after BIO creation and set the BIO as read only.
128 switch it to read only and call BIO_reset() on the read only BIO immediately
130 switched back to the read write mode.
132 Calling BIO_get_mem_ptr() on read only BIO will return a BUF_MEM that
[all …]
H A DSSL_rstate_string.pod5 …g, SSL_rstate_string_long - get textual description of state of an SSL object during read operation
16 SSL_rstate_string() returns a 2 letter string indicating the current read state
19 SSL_rstate_string_long() returns a string indicating the current read state of
24 When performing a read operation, the SSL/TLS engine must parse the record,
26 SSL_rstate_string[_long]() should always return "RD"/"read done".
37 =item "RH"/"read header"
41 =item "RB"/"read body"
47 The read state is unknown. This should never happen.
51 When used with QUIC SSL objects, these functions always return "RH"/"read
H A DBIO_f_readbuffer.pod6 - read only buffering BIO that supports BIO_tell() and BIO_seek()
16 BIO_f_readbuffer() returns the read buffering BIO method.
21 Data read from a read buffering BIO comes from an internal buffer which is
24 BIO_gets() is supported for read buffering BIOs.
25 Writing data to a read buffering BIO is not supported.
27 Calling BIO_reset() on a read buffering BIO does not clear any buffered data.
38 into data that is already read.
42 BIO_f_readbuffer() returns the read buffering BIO method.
H A DBIO_read.pod24 BIO_read_ex() attempts to read I<dlen> bytes from BIO I<b> and places the data
25 in I<data>. If any bytes were successfully read then the number of bytes read is
32 BIO_read() attempts to read I<len> bytes from BIO I<b> and places
36 in I<buf>. Usually this operation will attempt to read a line of data
59 BIO_read_ex() returns 1 if data was successfully read, and 0 otherwise.
71 Otherwise it typically returns the amount of data read,
73 the first NUL character contained in the data read.
74 In any case the trailing NUL that is added after the data read
79 read or written if the result is 0 or -1. If the return value is -2 then
91 and then call read() to read the data. The equivalent with BIOs (that is call
[all …]
H A DSSL_alloc_buffers.pod16 SSL_free_buffers() frees the read and write buffers of the given B<ssl>.
17 SSL_alloc_buffers() allocates the read and write buffers of the given B<ssl>.
19 The B<SSL_MODE_RELEASE_BUFFERS> mode releases read or write buffers whenever
24 new read or write. The SSL_alloc_buffers() does not need to be called, but
41 read or written. The SSL_alloc_buffers() function returns 0 when there is
H A DBIO_s_bio.pod34 BIOs where data written to either half of the pair is buffered and can be read from
46 Calls to BIO_read_ex() will read data from the buffer or request a retry if no
53 determine the amount of pending data in the read or write buffer.
65 been read.
88 last read attempt at the other half of the BIO pair failed due to an
90 written to the BIO so the next read will succeed: this is most useful
91 in TLS/SSL applications where the amount of data read is usually
92 meaningful rather than just a buffer size. After a successful read
94 has been written satisfying the read request or part of it.
171 buffer is full or the read buffer is drained. Then the application has to
[all …]
H A DSSL_CTX_set_read_ahead.pod8 - manage whether to read as many input bytes as possible
23 SSL_CTX_set_read_ahead() and SSL_set_read_ahead() set whether we should read as
26 the underlying BIO (where B<y> > B<x>), then OpenSSL will read all B<y> bytes
49 unprocessed data, it's recommended that if read ahead is turned on that
57 Otherwise the SSL structure might read data that it shouldn't.
H A DSSL_pending.pod19 read by the application via a call to L<SSL_read_ex(3)> or L<SSL_read(3)>.
22 and are available inside B<ssl> for immediate read.
26 record) may have been read containing more TLS/SSL records. This also applies to
31 the underlying BIO (because OpenSSL has already read them) and for SSL_pending()
48 bytes that are pending and are available for immediate read. SSL_has_pending()
H A DSSL_get_fd.pod19 read or the write channel, which can be different. If the read and the
21 of the read channel.
H A DSSL_CTX_set_split_send_fragment.pod55 "read" pipelining and "write" pipelining. By default only one pipeline will be
94 read as much data into the read buffer as the network can provide and will fit
95 into the buffer. Without this set data is read into the read buffer one record
96 at a time. The more data that can be read, the more opportunity there is for
100 read buffer is multiplied by the number of pipelines available to ensure that we
101 can read multiple records in one go. This can therefore have a significant
105 functions control the size of the read buffer that will be used. The B<len>
H A DBIO_f_buffer.pod30 to the next BIO in the chain. Data read from a buffering BIO comes from
39 set the read, write or both read and write buffer sizes to B<size>. The initial
44 BIO_set_buffer_read_data() clears the read buffer and fills it with B<num>
64 doing so will force a full read of the size of the internal buffer of
H A DBIO_s_dgram_pair.pod30 match that retrieved by a read call. If the buffer passed to a read call is too
31 short, the datagram is truncated or the read fails, depending on how the BIO is
35 and destination addresses. This information may be retrieved on read.
60 read.
72 size of the next datagram waiting to be read in bytes. An application can use
73 this function to ensure it provides an adequate buffer to a subsequent read
74 call. If no datagram is waiting to be read, zero is returned.
86 situation where an application attempts to read a datagram from a network
93 the next datagram to be read. If no-truncate mode is disabled (the default), the
129 example, if datagrams are queued with destination addresses set but simply read
H A DSSL_get_value_uint.pod99 read-write or read-only.
106 Values in this class are read-write, and represent what the local party is
110 A value in this class may become read-only in certain circumstances; for
121 Values in this value class are read-only, and represent what was requested by a
130 Values in this value class are read-only, and represent the value which was
134 Attempting to read a value in this class will generally fail if the feature
173 Generic read-only statistical value. The number of bidirectional,
275 Generic read-only statistical value. The size of the write buffer allocated to
285 Generic read-only statistical value. The number of bytes currently consumed
294 Generic read-only statistical value. The number of bytes available in the write
H A DRAND_load_file.pod21 up to B<max_bytes> are read;
22 if B<max_bytes> is -1, the complete file is read.
64 RAND_load_file() returns the number of bytes read or -1 on error.
H A DPEM_X509_INFO_read_bio_ex.pod6 - read PEM-encoded data structures into one or more B<X509_INFO> objects
42 The elements are read sequentially, and as far as they are of different type than
43 the elements read before, they are combined into the same B<X509_INFO> object.
H A DBIO_f_cipher.pod24 read from it. It is a BIO wrapper for the cipher routines
54 return value from the read operation. A successful decrypt followed
55 by EOF will also return zero for the final read. BIO_get_cipher_status()
H A DBIO_s_fd.pod21 round the platforms file descriptor routines such as read() and write().
23 BIO_read_ex() and BIO_write_ex() read or write the underlying descriptor.
49 platforms read() and write() calls on the descriptor. If the underlying
/openssl/doc/internal/man3/
H A Dossl_rcu_lock_new.pod12 - perform read-copy-update locking
39 Read-Copy-Update (RCU) locks, which allow for always nonblocking read paths.
73 ossl_rcu_read_lock() acquires a read side hold on data protected by
78 ossl_rcu_read_unlock() releases a read side hold on data protected by
84 the lock. Note only one writer per lock is permitted, as with read/write locks.
93 ossl_synchronize_rcu() blocks the calling thread until all read side
187 * 2) read the old pointer
209 * 6) wait for any read side holds on the old data
226 * 1) Acquire a read side hold on the shared data
H A Dossl_serial_number_print.pod17 number can be read into a long int, as well as hexadecimal. It notifies the
20 serial number cannot be read into a long int.
/openssl/doc/man1/
H A Dopenssl-passphrase-options.pod21 prompted to enter one: this will typically be read from the current
51 is read from the stream.
61 B<file:> applies to passwords read from file descriptors.
68 B<file:> applies to passwords read from standard input.
/openssl/include/internal/
H A Dsockets.h190 # define readsocket(s,b,n) read((s),(b),(n))
193 # define readsocket(s,b,n) read((s),(b),(n))
200 # define readsocket(s,b,n) read((s),(b),(n))
/openssl/doc/man7/
H A Dossl-guide-tls-client-non-block.pod28 until data is available to read if you attempt to read from it when there is no
34 to go and do other tasks whilst the socket is unable to read/write, for example
37 With a nonblocking socket attempting to read or write to a socket that is
38 currently unable to read or write will return immediately with a non-fatal
67 we want to read or write to the socket, but we are currently unable to. In fact
138 connection has failed), or non-fatal (for example because we are trying to read
152 if the application is only trying to read data. Similarly calls to
176 /* Temporary failure. Wait until we can read and try again */
305 * number of bytes that we read. The data could be non-printable or
316 response when trying to read data from the server. This will occur when the
[all …]
H A Dossl-guide-quic-client-non-block.pod30 it waits (blocks) until data is available to read if you attempt to read from
37 object is unable to read/write, for example updating a GUI or performing
43 error if they are currently unable to read or write respectively.
52 we want to read or write to the B<SSL> object but we are currently unable to.
87 * Find out if we would like to write to the socket, or read from it (or
129 application works. With a TLS application if we try to read or write something
132 read or write to the underlying socket and the socket signalled the "retry".
171 has failed), or non-fatal (for example because we are trying to read from the
393 * number of bytes that we read. The data could be non-printable or
404 response when trying to read data from the server. This will occur when the
[all …]
/openssl/doc/designs/quic-design/
H A Drecord-layer.md209 Libssl will read records by calling the `read_record` function. The
223 already been read from the underlying BIO, but not yet processed.
226 been read from the underlying BIO and has been processed. The data is not
230 buffered and available for immediate read.
233 that a previous attempt to read or write records failed.
375 * whether to use "read ahead" or not).
441 * available to read
513 * Release a buffer associated with a record previously read with
515 * are read.
599 * Free read or write buffers. Fails if there is pending read or write
[all …]

Completed in 67 milliseconds

123456789