Home
last modified time | relevance | path

Searched refs:write (Results 1 – 25 of 129) sorted by relevance

123456

/openssl-master/doc/man3/
A DSSL_write.pod5 SSL_write_ex, SSL_write, SSL_sendfile - write bytes to a TLS/SSL connection
31 In the paragraphs below a "write function" is defined as one of either
37 the write function operation. The behaviour of the write functions depends on the
43 before the first call to a write function.
46 the write operation has been finished or an error occurred.
51 return value of the write function will yield B<SSL_ERROR_WANT_READ>
64 partial write has been successfully completed. In this case the write function
67 write is performed with the size of a message block, which is 16kB.
101 The write operation was successful, the return value is the number of
122 The write operation was successful, the return value is the number
[all …]
A DBIO_s_mem.pod43 Calling BIO_reset() on a read write memory BIO clears any data in it if the
45 pointer to the state it was just after the last write was performed and the
83 Every write after partial read (not all data in the memory buffer was read)
92 Switching the memory BIO from read write to read only is not supported and
99 before switching it back to read write. Before the BIO is freed it must be
100 switched back to the read write mode.
108 Calling BIO_reset() on a read write memory BIO with BIO_FLAGS_NONCLEAR_RST
111 state after the last completed write operation. The effects of reads
112 preceding that write operation cannot be undone.
115 BIO_FLAGS_NONCLEAR_RST set has the same effect as a write operation.
[all …]
A DBIO_s_bio.pod53 determine the amount of pending data in the read or write buffer.
55 BIO_reset() clears any data in the write buffer.
67 BIO_set_write_buf_size() sets the write buffer size of BIO B<b> to B<size>.
71 BIO_get_write_buf_size() returns the size of the write buffer.
75 with write buffer sizes B<writebuf1> and B<writebuf2>. If either size is
107 flush any data in the write buffer. This can be done by calling BIO_pending()
117 transport before flushing the write buffer it will never succeed because the
170 connection, it behaves nonblocking and will return as soon as the write
172 flush the write buffer and/or fill the read buffer.
182 condition, but there is still data in the write buffer. An application must
[all …]
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
A DSSL_CTX_set_stateless_cookie_generate_cb.pod45 write at most SSL_COOKIE_LENGTH bytes into B<cookie>, and must write the number
60 app_gen_cookie_cb() must write at most DTLS1_COOKIE_LENGTH bytes into
61 B<cookie>, and must write the number of bytes written to B<cookie_len>. If a
A DBIO_read.pod28 BIO_write_ex() attempts to write I<dlen> bytes from I<data> to BIO I<b>.
53 BIO_write() attempts to write I<len> bytes from I<buf> to BIO I<b>.
55 BIO_puts() attempts to write a NUL-terminated string I<buf> to BIO I<b>.
62 Requesting to write 0 bytes is not considered an error.
64 BIO_write() returns -2 if the "write" operation is not implemented by the BIO
117 BIO_write_ex() returns 1 if the size of the data to write is 0 and the
A DPEM_read_bio_PrivateKey.pod199 The PEM functions read or write structures in PEM format. In
242 RSA structure. The write routines uses traditional format. The read
256 DSA structure. The write routines uses traditional format. The read
288 write functions use B<CERTIFICATE REQUEST> in the header whereas
304 or write to.
307 read from or write to.
318 The PEM functions which write private keys take an I<enc> parameter
326 For the PEM write routines if the I<kstr> parameter is not NULL then
365 The old B<PrivateKey> write routines are retained for compatibility.
366 New applications should write private keys using the
[all …]
A DSSL_CTX_set_tlsext_use_srtp.pod84 use. This provides the client write master key, the server write master key, the
85 client write master salt and the server write master salt in that order.
A DSSL_get_fd.pod19 read or the write channel, which can be different. If the read and the
20 write channel are different, SSL_get_fd() will return the file descriptor
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
A DBIO_f_buffer.pod39 set the read, write or both read and write buffer sizes to B<size>. The initial
67 Data is only written to the next BIO in the chain when the write buffer fills
A DSSL_CTX_set_mode.pod47 the behaviour of write().
54 nonblocking write().
68 incomplete read/write operations.
86 When we no longer need a read buffer or a write buffer for a given SSL,
A DBIO_f_base64.pod43 Base64 encode the string "Hello World\n" and write the result
57 Read Base64 encoded data from standard input and write the decoded
A DSSL_get_rbio.pod17 read or the write channel, which can be different. The reference count
A DBIO_should_retry.pod26 These functions determine why a BIO is not able to read or write data.
40 has pending data to write. Check for writability and/or retry the
112 that is they cannot retry after a partial read or write. This is usually
A DSSL_CTX_set_num_tickets.pod50 delayed until the server is starting a new write operation, so that it is
54 (without waiting for the next application write) by calling
A DUI_create_method.pod103 only write and don't assume the latter should only read.
106 For example, a typical tty reader wouldn't write the prompts in the
107 write, but would rather do so in the reader, because of the sequential
A DCMS_final.pod18 processed. The B<dcont> parameter contains a BIO to write content to after
A DSSL_CTX_set_split_send_fragment.pod37 connection. For example a single write can be split into multiple records and
55 "read" pipelining and "write" pipelining. By default only one pipeline will be
88 Read pipelining is controlled in a slightly different way than with write
A DCMS_EncryptedData_decrypt.pod19 symmetric I<key> of size I<keylen> bytes. I<out> is a BIO to write the content
A DBIO_s_socket.pod20 BIO_read_ex() and BIO_write_ex() read or write the underlying socket.
/openssl-master/include/internal/
A Dsockets.h149 # define writesocket(s,b,n) write((s),(char *)(b),(n))
157 # define writesocket(s,b,n) write((s),(b),(n))
165 # define writesocket(s,b,n) write((s),(b),(n))
/openssl-master/include/openssl/
A Dpem.h118 PEM_write_fnsig(name, type, FILE, write) \
130 PEM_write_cb_fnsig(name, type, FILE, write) \
240 attr PEM_write_fnsig(name, type, FILE, write);
242 attr PEM_write_fnsig(name, type, FILE, write); \
243 attr PEM_write_ex_fnsig(name, type, FILE, write);
246 attr PEM_write_fnsig(name, type, FILE, write);
249 attr PEM_write_cb_fnsig(name, type, FILE, write);
251 attr PEM_write_cb_fnsig(name, type, FILE, write); \
252 attr PEM_write_cb_ex_fnsig(name, type, FILE, write);
/openssl-master/crypto/pem/
A Dpem_local.h141 IMPLEMENT_PEM_provided_write_to(name, TYPE, type, str, asn1, FILE, fp, write)
143 IMPLEMENT_PEM_provided_write_cb_to(name, TYPE, type, str, asn1, FILE, fp, write)
/openssl-master/crypto/bio/
A Dbio_local.h187 # define UP_write write

Completed in 28 milliseconds

123456