forked from cory/tildefriends
Cory McWilliams
09ddfffa6b
git-svn-id: https://www.unprompted.com/svn/projects/tildefriends/trunk@4088 ed5197a5-7fde-0310-b194-c3ffbd925b24
276 lines
11 KiB
Groff
276 lines
11 KiB
Groff
.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.42)
|
|
.\"
|
|
.\" Standard preamble:
|
|
.\" ========================================================================
|
|
.de Sp \" Vertical space (when we can't use .PP)
|
|
.if t .sp .5v
|
|
.if n .sp
|
|
..
|
|
.de Vb \" Begin verbatim text
|
|
.ft CW
|
|
.nf
|
|
.ne \\$1
|
|
..
|
|
.de Ve \" End verbatim text
|
|
.ft R
|
|
.fi
|
|
..
|
|
.\" Set up some character translations and predefined strings. \*(-- will
|
|
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
|
|
.\" double quote, and \*(R" will give a right double quote. \*(C+ will
|
|
.\" give a nicer C++. Capital omega is used to do unbreakable dashes and
|
|
.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
|
|
.\" nothing in troff, for use with C<>.
|
|
.tr \(*W-
|
|
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
|
|
.ie n \{\
|
|
. ds -- \(*W-
|
|
. ds PI pi
|
|
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
|
|
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
|
|
. ds L" ""
|
|
. ds R" ""
|
|
. ds C` ""
|
|
. ds C' ""
|
|
'br\}
|
|
.el\{\
|
|
. ds -- \|\(em\|
|
|
. ds PI \(*p
|
|
. ds L" ``
|
|
. ds R" ''
|
|
. ds C`
|
|
. ds C'
|
|
'br\}
|
|
.\"
|
|
.\" Escape single quotes in literal strings from groff's Unicode transform.
|
|
.ie \n(.g .ds Aq \(aq
|
|
.el .ds Aq '
|
|
.\"
|
|
.\" If the F register is >0, we'll generate index entries on stderr for
|
|
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
|
|
.\" entries marked with X<> in POD. Of course, you'll have to process the
|
|
.\" output yourself in some meaningful fashion.
|
|
.\"
|
|
.\" Avoid warning from groff about undefined register 'F'.
|
|
.de IX
|
|
..
|
|
.nr rF 0
|
|
.if \n(.g .if rF .nr rF 1
|
|
.if (\n(rF:(\n(.g==0)) \{\
|
|
. if \nF \{\
|
|
. de IX
|
|
. tm Index:\\$1\t\\n%\t"\\$2"
|
|
..
|
|
. if !\nF==2 \{\
|
|
. nr % 0
|
|
. nr F 2
|
|
. \}
|
|
. \}
|
|
.\}
|
|
.rr rF
|
|
.\"
|
|
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
|
|
.\" Fear. Run. Save yourself. No user-serviceable parts.
|
|
. \" fudge factors for nroff and troff
|
|
.if n \{\
|
|
. ds #H 0
|
|
. ds #V .8m
|
|
. ds #F .3m
|
|
. ds #[ \f1
|
|
. ds #] \fP
|
|
.\}
|
|
.if t \{\
|
|
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
|
|
. ds #V .6m
|
|
. ds #F 0
|
|
. ds #[ \&
|
|
. ds #] \&
|
|
.\}
|
|
. \" simple accents for nroff and troff
|
|
.if n \{\
|
|
. ds ' \&
|
|
. ds ` \&
|
|
. ds ^ \&
|
|
. ds , \&
|
|
. ds ~ ~
|
|
. ds /
|
|
.\}
|
|
.if t \{\
|
|
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
|
|
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
|
|
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
|
|
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
|
|
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
|
|
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
|
|
.\}
|
|
. \" troff and (daisy-wheel) nroff accents
|
|
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
|
|
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
|
|
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
|
|
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
|
|
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
|
|
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
|
|
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
|
|
.ds ae a\h'-(\w'a'u*4/10)'e
|
|
.ds Ae A\h'-(\w'A'u*4/10)'E
|
|
. \" corrections for vroff
|
|
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
|
|
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
|
|
. \" for low resolution devices (crt and lpr)
|
|
.if \n(.H>23 .if \n(.V>19 \
|
|
\{\
|
|
. ds : e
|
|
. ds 8 ss
|
|
. ds o a
|
|
. ds d- d\h'-1'\(ga
|
|
. ds D- D\h'-1'\(hy
|
|
. ds th \o'bp'
|
|
. ds Th \o'LP'
|
|
. ds ae ae
|
|
. ds Ae AE
|
|
.\}
|
|
.rm #[ #] #H #V #F C
|
|
.\" ========================================================================
|
|
.\"
|
|
.IX Title "SSL_READ 3"
|
|
.TH SSL_READ 3 "2020-04-21" "1.1.1g" "OpenSSL"
|
|
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
|
|
.\" way too many mistakes in technical documents.
|
|
.if n .ad l
|
|
.nh
|
|
.SH "NAME"
|
|
SSL_read_ex, SSL_read, SSL_peek_ex, SSL_peek \&\- read bytes from a TLS/SSL connection
|
|
.SH "SYNOPSIS"
|
|
.IX Header "SYNOPSIS"
|
|
.Vb 1
|
|
\& #include <openssl/ssl.h>
|
|
\&
|
|
\& int SSL_read_ex(SSL *ssl, void *buf, size_t num, size_t *readbytes);
|
|
\& int SSL_read(SSL *ssl, void *buf, int num);
|
|
\&
|
|
\& int SSL_peek_ex(SSL *ssl, void *buf, size_t num, size_t *readbytes);
|
|
\& int SSL_peek(SSL *ssl, void *buf, int num);
|
|
.Ve
|
|
.SH "DESCRIPTION"
|
|
.IX Header "DESCRIPTION"
|
|
\&\fBSSL_read_ex()\fR and \fBSSL_read()\fR try to read \fBnum\fR bytes from the specified \fBssl\fR
|
|
into the buffer \fBbuf\fR. On success \fBSSL_read_ex()\fR will store the number of bytes
|
|
actually read in \fB*readbytes\fR.
|
|
.PP
|
|
\&\fBSSL_peek_ex()\fR and \fBSSL_peek()\fR are identical to \fBSSL_read_ex()\fR and \fBSSL_read()\fR
|
|
respectively except no bytes are actually removed from the underlying \s-1BIO\s0 during
|
|
the read, so that a subsequent call to \fBSSL_read_ex()\fR or \fBSSL_read()\fR will yield
|
|
at least the same bytes.
|
|
.SH "NOTES"
|
|
.IX Header "NOTES"
|
|
In the paragraphs below a \*(L"read function\*(R" is defined as one of \fBSSL_read_ex()\fR,
|
|
\&\fBSSL_read()\fR, \fBSSL_peek_ex()\fR or \fBSSL_peek()\fR.
|
|
.PP
|
|
If necessary, a read function will negotiate a \s-1TLS/SSL\s0 session, if not already
|
|
explicitly performed by \fBSSL_connect\fR\|(3) or \fBSSL_accept\fR\|(3). If the
|
|
peer requests a re-negotiation, it will be performed transparently during
|
|
the read function operation. The behaviour of the read functions depends on the
|
|
underlying \s-1BIO.\s0
|
|
.PP
|
|
For the transparent negotiation to succeed, the \fBssl\fR must have been
|
|
initialized to client or server mode. This is being done by calling
|
|
\&\fBSSL_set_connect_state\fR\|(3) or \fBSSL_set_accept_state()\fR before the first
|
|
invocation of a read function.
|
|
.PP
|
|
The read functions work based on the \s-1SSL/TLS\s0 records. The data are received in
|
|
records (with a maximum record size of 16kB). Only when a record has been
|
|
completely received, can it be processed (decryption and check of integrity).
|
|
Therefore data that was not retrieved at the last read call can still be
|
|
buffered inside the \s-1SSL\s0 layer and will be retrieved on the next read
|
|
call. If \fBnum\fR is higher than the number of bytes buffered then the read
|
|
functions will return with the bytes buffered. If no more bytes are in the
|
|
buffer, the read functions will trigger the processing of the next record.
|
|
Only when the record has been received and processed completely will the read
|
|
functions return reporting success. At most the contents of one record will
|
|
be returned. As the size of an \s-1SSL/TLS\s0 record may exceed the maximum packet size
|
|
of the underlying transport (e.g. \s-1TCP\s0), it may be necessary to read several
|
|
packets from the transport layer before the record is complete and the read call
|
|
can succeed.
|
|
.PP
|
|
If \fB\s-1SSL_MODE_AUTO_RETRY\s0\fR has been switched off and a non-application data
|
|
record has been processed, the read function can return and set the error to
|
|
\&\fB\s-1SSL_ERROR_WANT_READ\s0\fR.
|
|
In this case there might still be unprocessed data available in the \fB\s-1BIO\s0\fR.
|
|
If read ahead was set using \fBSSL_CTX_set_read_ahead\fR\|(3), there might also still
|
|
be unprocessed data available in the \fB\s-1SSL\s0\fR.
|
|
This behaviour can be controlled using the \fBSSL_CTX_set_mode\fR\|(3) call.
|
|
.PP
|
|
If the underlying \s-1BIO\s0 is \fBblocking\fR, a read function will only return once the
|
|
read operation has been finished or an error occurred, except when a
|
|
non-application data record has been processed and \fB\s-1SSL_MODE_AUTO_RETRY\s0\fR is
|
|
not set.
|
|
Note that if \fB\s-1SSL_MODE_AUTO_RETRY\s0\fR is set and only non-application data is
|
|
available the call will hang.
|
|
.PP
|
|
If the underlying \s-1BIO\s0 is \fBnon-blocking\fR, a read function will also return when
|
|
the underlying \s-1BIO\s0 could not satisfy the needs of the function to continue the
|
|
operation.
|
|
In this case a call to \fBSSL_get_error\fR\|(3) with the
|
|
return value of the read function will yield \fB\s-1SSL_ERROR_WANT_READ\s0\fR or
|
|
\&\fB\s-1SSL_ERROR_WANT_WRITE\s0\fR.
|
|
As at any time it's possible that non-application data needs to be sent,
|
|
a read function can also cause write operations.
|
|
The calling process then must repeat the call after taking appropriate action
|
|
to satisfy the needs of the read function.
|
|
The action depends on the underlying \s-1BIO.\s0
|
|
When using a non-blocking socket, nothing is to be done, but \fBselect()\fR can be
|
|
used to check for the required condition.
|
|
When using a buffering \s-1BIO,\s0 like a \s-1BIO\s0 pair, data must be written into or
|
|
retrieved out of the \s-1BIO\s0 before being able to continue.
|
|
.PP
|
|
\&\fBSSL_pending\fR\|(3) can be used to find out whether there
|
|
are buffered bytes available for immediate retrieval.
|
|
In this case the read function can be called without blocking or actually
|
|
receiving new data from the underlying socket.
|
|
.SH "RETURN VALUES"
|
|
.IX Header "RETURN VALUES"
|
|
\&\fBSSL_read_ex()\fR and \fBSSL_peek_ex()\fR will return 1 for success or 0 for failure.
|
|
Success means that 1 or more application data bytes have been read from the \s-1SSL\s0
|
|
connection.
|
|
Failure means that no bytes could be read from the \s-1SSL\s0 connection.
|
|
Failures can be retryable (e.g. we are waiting for more bytes to
|
|
be delivered by the network) or non-retryable (e.g. a fatal network error).
|
|
In the event of a failure call \fBSSL_get_error\fR\|(3) to find out the reason which
|
|
indicates whether the call is retryable or not.
|
|
.PP
|
|
For \fBSSL_read()\fR and \fBSSL_peek()\fR the following return values can occur:
|
|
.IP "> 0" 4
|
|
.IX Item "> 0"
|
|
The read operation was successful.
|
|
The return value is the number of bytes actually read from the \s-1TLS/SSL\s0
|
|
connection.
|
|
.IP "<= 0" 4
|
|
.IX Item "<= 0"
|
|
The read operation was not successful, because either the connection was closed,
|
|
an error occurred or action must be taken by the calling process.
|
|
Call \fBSSL_get_error\fR\|(3) with the return value \fBret\fR to find out the reason.
|
|
.Sp
|
|
Old documentation indicated a difference between 0 and \-1, and that \-1 was
|
|
retryable.
|
|
You should instead call \fBSSL_get_error()\fR to find out if it's retryable.
|
|
.SH "SEE ALSO"
|
|
.IX Header "SEE ALSO"
|
|
\&\fBSSL_get_error\fR\|(3), \fBSSL_write_ex\fR\|(3),
|
|
\&\fBSSL_CTX_set_mode\fR\|(3), \fBSSL_CTX_new\fR\|(3),
|
|
\&\fBSSL_connect\fR\|(3), \fBSSL_accept\fR\|(3)
|
|
\&\fBSSL_set_connect_state\fR\|(3),
|
|
\&\fBSSL_pending\fR\|(3),
|
|
\&\fBSSL_shutdown\fR\|(3), \fBSSL_set_shutdown\fR\|(3),
|
|
\&\fBssl\fR\|(7), \fBbio\fR\|(7)
|
|
.SH "HISTORY"
|
|
.IX Header "HISTORY"
|
|
The \fBSSL_read_ex()\fR and \fBSSL_peek_ex()\fR functions were added in OpenSSL 1.1.1.
|
|
.SH "COPYRIGHT"
|
|
.IX Header "COPYRIGHT"
|
|
Copyright 2000\-2019 The OpenSSL Project Authors. All Rights Reserved.
|
|
.PP
|
|
Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
|
|
this file except in compliance with the License. You can obtain a copy
|
|
in the file \s-1LICENSE\s0 in the source distribution or at
|
|
<https://www.openssl.org/source/license.html>.
|