bio_s_null(3) [centos man page]

BIO_s_null(3)							      OpenSSL							     BIO_s_null(3)

NAME

       BIO_s_null - null data sink

SYNOPSIS

	#include <openssl/bio.h>

	BIO_METHOD *   BIO_s_null(void);

DESCRIPTION

       BIO_s_null() returns the null sink BIO method. Data written to the null sink is discarded, reads return EOF.

NOTES

       A null sink BIO behaves in a similar manner to the Unix /dev/null device.

       A null bio can be placed on the end of a chain to discard any data passed through it.

       A null sink is useful if, for example, an application wishes to digest some data by writing through a digest bio but not send the digested
       data anywhere.  Since a BIO chain must normally include a source/sink BIO this can be achieved by adding a null sink BIO to the end of the
       chain

RETURN VALUES

       BIO_s_null() returns the null sink BIO method.

SEE ALSO

       TBA

1.0.1e								    2013-02-11							     BIO_s_null(3)

bio(3)								      OpenSSL								    bio(3)

NAME

       bio - I/O abstraction

SYNOPSIS

	#include <openssl/bio.h>

       TBA

DESCRIPTION

       A BIO is an I/O abstraction, it hides many of the underlying I/O details from an application. If an application uses a BIO for its I/O it
       can transparently handle SSL connections, unencrypted network connections and file I/O.

       There are two type of BIO, a source/sink BIO and a filter BIO.

       As its name implies a source/sink BIO is a source and/or sink of data, examples include a socket BIO and a file BIO.

       A filter BIO takes data from one BIO and passes it through to another, or the application. The data may be left unmodified (for example a
       message digest BIO) or translated (for example an encryption BIO). The effect of a filter BIO may change according to the I/O operation it
       is performing: for example an encryption BIO will encrypt data if it is being written to and decrypt data if it is being read from.

       BIOs can be joined together to form a chain (a single BIO is a chain with one component). A chain normally consist of one source/sink BIO
       and one or more filter BIOs. Data read from or written to the first BIO then traverses the chain to the end (normally a source/sink BIO).

SEE ALSO

       BIO_ctrl(3), BIO_f_base64(3), BIO_f_buffer(3), BIO_f_cipher(3), BIO_f_md(3), BIO_f_null(3), BIO_f_ssl(3), BIO_find_type(3), BIO_new(3),
       BIO_new_bio_pair(3), BIO_push(3), BIO_read(3), BIO_s_accept(3), BIO_s_bio(3), BIO_s_connect(3), BIO_s_fd(3), BIO_s_file(3), BIO_s_mem(3),
       BIO_s_null(3), BIO_s_socket(3), BIO_set_callback(3), BIO_should_retry(3)

50								    2013-03-05								    bio(3)