mirror of
https://github.com/openssl/openssl.git
synced 2024-12-15 06:01:37 +08:00
f505161e62
Revert a change in behavior to BIO_write(). If a NULL BIO is passed, no error is raised and the return value is 0. There are many places where the return code from the write was not checked, resulting in an error stack with no error status being returned. Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/15493)
121 lines
4.7 KiB
Plaintext
121 lines
4.7 KiB
Plaintext
=pod
|
|
|
|
=head1 NAME
|
|
|
|
BIO_read_ex, BIO_write_ex, BIO_read, BIO_write,
|
|
BIO_gets, BIO_get_line, BIO_puts
|
|
- BIO I/O functions
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
#include <openssl/bio.h>
|
|
|
|
int BIO_read_ex(BIO *b, void *data, size_t dlen, size_t *readbytes);
|
|
int BIO_write_ex(BIO *b, const void *data, size_t dlen, size_t *written);
|
|
|
|
int BIO_read(BIO *b, void *data, int dlen);
|
|
int BIO_gets(BIO *b, char *buf, int size);
|
|
int BIO_get_line(BIO *b, char *buf, int size);
|
|
int BIO_write(BIO *b, const void *data, int dlen);
|
|
int BIO_puts(BIO *b, const char *buf);
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
BIO_read_ex() attempts to read I<dlen> bytes from BIO I<b> and places the data
|
|
in I<data>. If any bytes were successfully read then the number of bytes read is
|
|
stored in I<*readbytes>.
|
|
|
|
BIO_write_ex() attempts to write I<dlen> bytes from I<data> to BIO I<b>. If
|
|
successful then the number of bytes written is stored in I<*written>.
|
|
|
|
BIO_read() attempts to read I<len> bytes from BIO I<b> and places
|
|
the data in I<buf>.
|
|
|
|
BIO_gets() performs the BIOs "gets" operation and places the data
|
|
in I<buf>. Usually this operation will attempt to read a line of data
|
|
from the BIO of maximum length I<size-1>. There are exceptions to this,
|
|
however; for example, BIO_gets() on a digest BIO will calculate and
|
|
return the digest and other BIOs may not support BIO_gets() at all.
|
|
The returned string is always NUL-terminated and the '\n' is preserved
|
|
if present in the input data.
|
|
On binary input there may be NUL characters within the string;
|
|
in this case the return value (if nonnegative) may give an incorrect length.
|
|
|
|
BIO_get_line() attempts to read from BIO <b> a line of data up to the next '\n'
|
|
or the maximum length I<size-1> is reached and places the data in I<buf>.
|
|
The returned string is always NUL-terminated and the '\n' is preserved
|
|
if present in the input data.
|
|
On binary input there may be NUL characters within the string;
|
|
in this case the return value (if nonnegative) gives the actual length read.
|
|
For implementing this, unfortunately the data needs to be read byte-by-byte.
|
|
|
|
BIO_write() attempts to write I<len> bytes from I<buf> to BIO I<b>.
|
|
|
|
BIO_puts() attempts to write a NUL-terminated string I<buf> to BIO I<b>.
|
|
|
|
=head1 RETURN VALUES
|
|
|
|
BIO_read_ex() and BIO_write_ex() return 1 if data was successfully read or
|
|
written, and 0 otherwise.
|
|
|
|
BIO_write() and BIO_write_ex() return 0 if the BIO I<b> is NULL.
|
|
|
|
BIO_gets() returns -2 if the "gets" operation is not implemented by the BIO
|
|
or -1 on other errors.
|
|
Otherwise it typically returns the amount of data read,
|
|
but depending on the implementation it may return only the length up to
|
|
the first NUL character contained in the data read.
|
|
In any case the trailing NUL that is added after the data read
|
|
is not included in the length returned.
|
|
|
|
All other functions return either the amount of data successfully read or
|
|
written (if the return value is positive) or that no data was successfully
|
|
read or written if the result is 0 or -1. If the return value is -2 then
|
|
the operation is not implemented in the specific BIO type.
|
|
|
|
=head1 NOTES
|
|
|
|
A 0 or -1 return is not necessarily an indication of an error. In
|
|
particular when the source/sink is nonblocking or of a certain type
|
|
it may merely be an indication that no data is currently available and that
|
|
the application should retry the operation later.
|
|
|
|
One technique sometimes used with blocking sockets is to use a system call
|
|
(such as select(), poll() or equivalent) to determine when data is available
|
|
and then call read() to read the data. The equivalent with BIOs (that is call
|
|
select() on the underlying I/O structure and then call BIO_read() to
|
|
read the data) should B<not> be used because a single call to BIO_read()
|
|
can cause several reads (and writes in the case of SSL BIOs) on the underlying
|
|
I/O structure and may block as a result. Instead select() (or equivalent)
|
|
should be combined with non blocking I/O so successive reads will request
|
|
a retry instead of blocking.
|
|
|
|
See L<BIO_should_retry(3)> for details of how to
|
|
determine the cause of a retry and other I/O issues.
|
|
|
|
If the "gets" method is not supported by a BIO then BIO_get_line() can be used.
|
|
It is also possible to make BIO_gets() usable even if the "gets" method is not
|
|
supported by adding a buffering BIO L<BIO_f_buffer(3)> to the chain.
|
|
|
|
=head1 SEE ALSO
|
|
|
|
L<BIO_should_retry(3)>
|
|
|
|
=head1 HISTORY
|
|
|
|
BIO_gets() on 1.1.0 and older when called on BIO_fd() based BIO did not
|
|
keep the '\n' at the end of the line in the buffer.
|
|
|
|
BIO_get_line() was added in OpenSSL 3.0.
|
|
|
|
=head1 COPYRIGHT
|
|
|
|
Copyright 2000-2021 The OpenSSL Project Authors. All Rights Reserved.
|
|
|
|
Licensed under the Apache License 2.0 (the "License"). You may not use
|
|
this file except in compliance with the License. You can obtain a copy
|
|
in the file LICENSE in the source distribution or at
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
=cut
|