1 .\" $NetBSD: libcrypto.pl,v 1.3 2007/11/27 22:16:03 christos Exp $
3 .\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
6 .\" ========================================================================
7 .de Sh \" Subsection heading
15 .de Sp \" Vertical space (when we can't use .PP)
19 .de Vb \" Begin verbatim text
24 .de Ve \" End verbatim text
28 .\" Set up some character translations and predefined strings. \*(-- will
29 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
30 .\" double quote, and \*(R" will give a right double quote. \*(C+ will
31 .\" give a nicer C++. Capital omega is used to do unbreakable dashes and
32 .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
33 .\" nothing in troff, for use with C<>.
35 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
39 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
40 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
53 .\" Escape single quotes in literal strings from groff's Unicode transform.
57 .\" If the F register is turned on, we'll generate index entries on stderr for
58 .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
59 .\" entries marked with X<> in POD. Of course, you'll have to process the
60 .\" output yourself in some meaningful fashion.
63 . tm Index:\\$1\t\\n%\t"\\$2"
73 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
74 .\" Fear. Run. Save yourself. No user-serviceable parts.
75 . \" fudge factors for nroff and troff
84 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
90 . \" simple accents for nroff and troff
100 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
101 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
102 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
103 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
104 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
105 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
107 . \" troff and (daisy-wheel) nroff accents
108 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
109 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
110 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
111 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
112 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
113 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
114 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
115 .ds ae a\h'-(\w'a'u*4/10)'e
116 .ds Ae A\h'-(\w'A'u*4/10)'E
117 . \" corrections for vroff
118 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
119 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
120 . \" for low resolution devices (crt and lpr)
121 .if \n(.H>23 .if \n(.V>19 \
134 .\" ========================================================================
136 .IX Title "SSL_write 3"
137 .TH SSL_write 3 "2002-07-19" "1.1.0-dev" "OpenSSL"
138 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
139 .\" way too many mistakes in technical documents.
143 SSL_write \- write bytes to a TLS/SSL connection.
147 .IX Header "SYNOPSIS"
149 \& #include <openssl/ssl.h>
151 \& int SSL_write(SSL *ssl, const void *buf, int num);
154 .IX Header "DESCRIPTION"
155 \&\fISSL_write()\fR writes \fBnum\fR bytes from the buffer \fBbuf\fR into the specified
156 \&\fBssl\fR connection.
159 If necessary, \fISSL_write()\fR will negotiate a \s-1TLS/SSL\s0 session, if
160 not already explicitly performed by \fISSL_connect\fR\|(3) or
161 \&\fISSL_accept\fR\|(3). If the
162 peer requests a re-negotiation, it will be performed transparently during
163 the \fISSL_write()\fR operation. The behaviour of \fISSL_write()\fR depends on the
164 underlying \s-1BIO\s0.
166 For the transparent negotiation to succeed, the \fBssl\fR must have been
167 initialized to client or server mode. This is being done by calling
168 \&\fISSL_set_connect_state\fR\|(3) or \fISSL_set_accept_state()\fR
169 before the first call to an \fISSL_read\fR\|(3) or \fISSL_write()\fR function.
171 If the underlying \s-1BIO\s0 is \fBblocking\fR, \fISSL_write()\fR will only return, once the
172 write operation has been finished or an error occurred, except when a
173 renegotiation take place, in which case a \s-1SSL_ERROR_WANT_READ\s0 may occur.
174 This behaviour can be controlled with the \s-1SSL_MODE_AUTO_RETRY\s0 flag of the
175 \&\fISSL_CTX_set_mode\fR\|(3) call.
177 If the underlying \s-1BIO\s0 is \fBnon-blocking\fR, \fISSL_write()\fR will also return,
178 when the underlying \s-1BIO\s0 could not satisfy the needs of \fISSL_write()\fR
179 to continue the operation. In this case a call to
180 \&\fISSL_get_error\fR\|(3) with the
181 return value of \fISSL_write()\fR will yield \fB\s-1SSL_ERROR_WANT_READ\s0\fR or
182 \&\fB\s-1SSL_ERROR_WANT_WRITE\s0\fR. As at any time a re-negotiation is possible, a
183 call to \fISSL_write()\fR can also cause read operations! The calling process
184 then must repeat the call after taking appropriate action to satisfy the
185 needs of \fISSL_write()\fR. The action depends on the underlying \s-1BIO\s0. When using a
186 non-blocking socket, nothing is to be done, but \fIselect()\fR can be used to check
187 for the required condition. When using a buffering \s-1BIO\s0, like a \s-1BIO\s0 pair, data
188 must be written into or retrieved out of the \s-1BIO\s0 before being able to continue.
190 \&\fISSL_write()\fR will only return with success, when the complete contents
191 of \fBbuf\fR of length \fBnum\fR has been written. This default behaviour
192 can be changed with the \s-1SSL_MODE_ENABLE_PARTIAL_WRITE\s0 option of
193 \&\fISSL_CTX_set_mode\fR\|(3). When this flag is set,
194 \&\fISSL_write()\fR will also return with success, when a partial write has been
195 successfully completed. In this case the \fISSL_write()\fR operation is considered
196 completed. The bytes are sent and a new \fISSL_write()\fR operation with a new
197 buffer (with the already sent bytes removed) must be started.
198 A partial write is performed with the size of a message block, which is
199 16kB for SSLv3/TLSv1.
202 When an \fISSL_write()\fR operation has to be repeated because of
203 \&\fB\s-1SSL_ERROR_WANT_READ\s0\fR or \fB\s-1SSL_ERROR_WANT_WRITE\s0\fR, it must be repeated
204 with the same arguments.
206 When calling \fISSL_write()\fR with num=0 bytes to be sent the behaviour is
209 .IX Header "RETURN VALUES"
210 The following return values can occur:
213 The write operation was successful, the return value is the number of
214 bytes actually written to the \s-1TLS/SSL\s0 connection.
216 The write operation was not successful. Probably the underlying connection
217 was closed. Call \fISSL_get_error()\fR with the return value \fBret\fR to find out,
218 whether an error occurred or the connection was shut down cleanly
219 (\s-1SSL_ERROR_ZERO_RETURN\s0).
221 SSLv2 (deprecated) does not support a shutdown alert protocol, so it can
222 only be detected, whether the underlying connection was closed. It cannot
223 be checked, why the closure happened.
226 The write operation was not successful, because either an error occurred
227 or action must be taken by the calling process. Call \fISSL_get_error()\fR with the
228 return value \fBret\fR to find out the reason.
230 .IX Header "SEE ALSO"
231 \&\fISSL_get_error\fR\|(3), \fISSL_read\fR\|(3),
232 \&\fISSL_CTX_set_mode\fR\|(3), \fISSL_CTX_new\fR\|(3),
233 \&\fISSL_connect\fR\|(3), \fISSL_accept\fR\|(3)
234 \&\fISSL_set_connect_state\fR\|(3),
235 \&\fIssl\fR\|(3), \fIopenssl_bio\fR\|(3)