Upgrade to OpenSSL-1.0.0d.
[dragonfly.git] / secure / lib / libssl / man / SSL_write.3
... / ...
CommitLineData
1.\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14)
2.\"
3.\" Standard preamble:
4.\" ========================================================================
5.de Sp \" Vertical space (when we can't use .PP)
6.if t .sp .5v
7.if n .sp
8..
9.de Vb \" Begin verbatim text
10.ft CW
11.nf
12.ne \\$1
13..
14.de Ve \" End verbatim text
15.ft R
16.fi
17..
18.\" Set up some character translations and predefined strings. \*(-- will
19.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
20.\" double quote, and \*(R" will give a right double quote. \*(C+ will
21.\" give a nicer C++. Capital omega is used to do unbreakable dashes and
22.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
23.\" nothing in troff, for use with C<>.
24.tr \(*W-
25.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
26.ie n \{\
27. ds -- \(*W-
28. ds PI pi
29. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
31. ds L" ""
32. ds R" ""
33. ds C` ""
34. ds C' ""
35'br\}
36.el\{\
37. ds -- \|\(em\|
38. ds PI \(*p
39. ds L" ``
40. ds R" ''
41'br\}
42.\"
43.\" Escape single quotes in literal strings from groff's Unicode transform.
44.ie \n(.g .ds Aq \(aq
45.el .ds Aq '
46.\"
47.\" If the F register is turned on, we'll generate index entries on stderr for
48.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
49.\" entries marked with X<> in POD. Of course, you'll have to process the
50.\" output yourself in some meaningful fashion.
51.ie \nF \{\
52. de IX
53. tm Index:\\$1\t\\n%\t"\\$2"
54..
55. nr % 0
56. rr F
57.\}
58.el \{\
59. de IX
60..
61.\}
62.\"
63.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
64.\" Fear. Run. Save yourself. No user-serviceable parts.
65. \" fudge factors for nroff and troff
66.if n \{\
67. ds #H 0
68. ds #V .8m
69. ds #F .3m
70. ds #[ \f1
71. ds #] \fP
72.\}
73.if t \{\
74. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
75. ds #V .6m
76. ds #F 0
77. ds #[ \&
78. ds #] \&
79.\}
80. \" simple accents for nroff and troff
81.if n \{\
82. ds ' \&
83. ds ` \&
84. ds ^ \&
85. ds , \&
86. ds ~ ~
87. ds /
88.\}
89.if t \{\
90. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
91. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
92. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
93. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
94. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
95. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
96.\}
97. \" troff and (daisy-wheel) nroff accents
98.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
99.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
100.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
101.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
102.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
103.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
104.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
105.ds ae a\h'-(\w'a'u*4/10)'e
106.ds Ae A\h'-(\w'A'u*4/10)'E
107. \" corrections for vroff
108.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
109.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
110. \" for low resolution devices (crt and lpr)
111.if \n(.H>23 .if \n(.V>19 \
112\{\
113. ds : e
114. ds 8 ss
115. ds o a
116. ds d- d\h'-1'\(ga
117. ds D- D\h'-1'\(hy
118. ds th \o'bp'
119. ds Th \o'LP'
120. ds ae ae
121. ds Ae AE
122.\}
123.rm #[ #] #H #V #F C
124.\" ========================================================================
125.\"
126.IX Title "SSL_write 3"
127.TH SSL_write 3 "2011-02-08" "1.0.0d" "OpenSSL"
128.\" For nroff, turn off justification. Always turn off hyphenation; it makes
129.\" way too many mistakes in technical documents.
130.if n .ad l
131.nh
132.SH "NAME"
133SSL_write \- write bytes to a TLS/SSL connection.
134.SH "SYNOPSIS"
135.IX Header "SYNOPSIS"
136.Vb 1
137\& #include <openssl/ssl.h>
138\&
139\& int SSL_write(SSL *ssl, const void *buf, int num);
140.Ve
141.SH "DESCRIPTION"
142.IX Header "DESCRIPTION"
143\&\fISSL_write()\fR writes \fBnum\fR bytes from the buffer \fBbuf\fR into the specified
144\&\fBssl\fR connection.
145.SH "NOTES"
146.IX Header "NOTES"
147If necessary, \fISSL_write()\fR will negotiate a \s-1TLS/SSL\s0 session, if
148not already explicitly performed by \fISSL_connect\fR\|(3) or
149\&\fISSL_accept\fR\|(3). If the
150peer requests a re-negotiation, it will be performed transparently during
151the \fISSL_write()\fR operation. The behaviour of \fISSL_write()\fR depends on the
152underlying \s-1BIO\s0.
153.PP
154For the transparent negotiation to succeed, the \fBssl\fR must have been
155initialized to client or server mode. This is being done by calling
156\&\fISSL_set_connect_state\fR\|(3) or \fISSL_set_accept_state()\fR
157before the first call to an \fISSL_read\fR\|(3) or \fISSL_write()\fR function.
158.PP
159If the underlying \s-1BIO\s0 is \fBblocking\fR, \fISSL_write()\fR will only return, once the
160write operation has been finished or an error occurred, except when a
161renegotiation take place, in which case a \s-1SSL_ERROR_WANT_READ\s0 may occur.
162This behaviour can be controlled with the \s-1SSL_MODE_AUTO_RETRY\s0 flag of the
163\&\fISSL_CTX_set_mode\fR\|(3) call.
164.PP
165If the underlying \s-1BIO\s0 is \fBnon-blocking\fR, \fISSL_write()\fR will also return,
166when the underlying \s-1BIO\s0 could not satisfy the needs of \fISSL_write()\fR
167to continue the operation. In this case a call to
168\&\fISSL_get_error\fR\|(3) with the
169return value of \fISSL_write()\fR will yield \fB\s-1SSL_ERROR_WANT_READ\s0\fR or
170\&\fB\s-1SSL_ERROR_WANT_WRITE\s0\fR. As at any time a re-negotiation is possible, a
171call to \fISSL_write()\fR can also cause read operations! The calling process
172then must repeat the call after taking appropriate action to satisfy the
173needs of \fISSL_write()\fR. The action depends on the underlying \s-1BIO\s0. When using a
174non-blocking socket, nothing is to be done, but \fIselect()\fR can be used to check
175for the required condition. When using a buffering \s-1BIO\s0, like a \s-1BIO\s0 pair, data
176must be written into or retrieved out of the \s-1BIO\s0 before being able to continue.
177.PP
178\&\fISSL_write()\fR will only return with success, when the complete contents
179of \fBbuf\fR of length \fBnum\fR has been written. This default behaviour
180can be changed with the \s-1SSL_MODE_ENABLE_PARTIAL_WRITE\s0 option of
181\&\fISSL_CTX_set_mode\fR\|(3). When this flag is set,
182\&\fISSL_write()\fR will also return with success, when a partial write has been
183successfully completed. In this case the \fISSL_write()\fR operation is considered
184completed. The bytes are sent and a new \fISSL_write()\fR operation with a new
185buffer (with the already sent bytes removed) must be started.
186A partial write is performed with the size of a message block, which is
18716kB for SSLv3/TLSv1.
188.SH "WARNING"
189.IX Header "WARNING"
190When an \fISSL_write()\fR operation has to be repeated because of
191\&\fB\s-1SSL_ERROR_WANT_READ\s0\fR or \fB\s-1SSL_ERROR_WANT_WRITE\s0\fR, it must be repeated
192with the same arguments.
193.PP
194When calling \fISSL_write()\fR with num=0 bytes to be sent the behaviour is
195undefined.
196.SH "RETURN VALUES"
197.IX Header "RETURN VALUES"
198The following return values can occur:
199.IP ">0" 4
200.IX Item ">0"
201The write operation was successful, the return value is the number of
202bytes actually written to the \s-1TLS/SSL\s0 connection.
203.IP "0" 4
204The write operation was not successful. Probably the underlying connection
205was closed. Call \fISSL_get_error()\fR with the return value \fBret\fR to find out,
206whether an error occurred or the connection was shut down cleanly
207(\s-1SSL_ERROR_ZERO_RETURN\s0).
208.Sp
209SSLv2 (deprecated) does not support a shutdown alert protocol, so it can
210only be detected, whether the underlying connection was closed. It cannot
211be checked, why the closure happened.
212.IP "<0" 4
213.IX Item "<0"
214The write operation was not successful, because either an error occurred
215or action must be taken by the calling process. Call \fISSL_get_error()\fR with the
216return value \fBret\fR to find out the reason.
217.SH "SEE ALSO"
218.IX Header "SEE ALSO"
219\&\fISSL_get_error\fR\|(3), \fISSL_read\fR\|(3),
220\&\fISSL_CTX_set_mode\fR\|(3), \fISSL_CTX_new\fR\|(3),
221\&\fISSL_connect\fR\|(3), \fISSL_accept\fR\|(3)
222\&\fISSL_set_connect_state\fR\|(3),
223\&\fIssl\fR\|(3), \fIbio\fR\|(3)