|
|
|
BF_ecb_encrypt(3) -- Blowfish encryption
|
|
This library implements the Blowfish cipher, which was invented and described by Counterpane. See http://www.counterpane.com/blowfish.html. Blowfish is a block cipher that operates on 64-bit (8 byte) ... |
|
BF_encrypt(3) -- Blowfish encryption
|
|
This library implements the Blowfish cipher, which was invented and described by Counterpane. See http://www.counterpane.com/blowfish.html. Blowfish is a block cipher that operates on 64-bit (8 byte) ... |
|
|
BF_ofb64_encrypt(3) -- Blowfish encryption
|
|
This library implements the Blowfish cipher, which was invented and described by Counterpane. See http://www.counterpane.com/blowfish.html. Blowfish is a block cipher that operates on 64-bit (8 byte) ... |
|
BF_options(3) -- Blowfish encryption
|
|
This library implements the Blowfish cipher, which was invented and described by Counterpane. See http://www.counterpane.com/blowfish.html. Blowfish is a block cipher that operates on 64-bit (8 byte) ... |
|
BF_set_key(3) -- Blowfish encryption
|
|
This library implements the Blowfish cipher, which was invented and described by Counterpane. See http://www.counterpane.com/blowfish.html. Blowfish is a block cipher that operates on 64-bit (8 byte) ... |
|
bindresvport(3) -- Bind a socket to a privileged IP port
|
|
The bindresvport() function is used to bind a socket descriptor to a privileged IP port, that is, a port number in the range 0-1023. The routine returns 0 if it is successful, otherwise -1 is returned... |
|
bind_to_cpu(3) -- Bind execution to a specific CPU
|
|
Upon return from bind_to_cpu() or bind_to_cpu_id(), all threads of the target pid are running on the target CPU. Bound threads are not eligible for execution on any other CPU. You release CPU binding ... |
|
bind_to_cpu_id(3) -- Bind execution to a specific CPU
|
|
Upon return from bind_to_cpu() or bind_to_cpu_id(), all threads of the target pid are running on the target CPU. Bound threads are not eligible for execution on any other CPU. You release CPU binding ... |
|
bio(3) -- I/O abstraction
|
|
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 ... |
|
BIO_append_filename(3) -- FILE bio
|
|
The BIO_s_file() function returns the BIO file method. As its name implies it is a wrapper round the stdio FILE structure and it is a source/sink BIO. Calls to BIO_read() and BIO_write() read and writ... |
|
BIO_callback_ctrl(3) -- BIO control operations
|
|
The BIO_ctrl(), BIO_callback_ctrl(), BIO_ptr_ctrl(), and BIO_int_ctrl() functions are BIO control operations taking arguments of various types. These functions are not usually called directly; various... |
|
BIO_ctrl(3) -- BIO control operations
|
|
The BIO_ctrl(), BIO_callback_ctrl(), BIO_ptr_ctrl(), and BIO_int_ctrl() functions are BIO control operations taking arguments of various types. These functions are not usually called directly; various... |
|
BIO_ctrl_get_read_request(3) -- Find out how many bytes were requested from the BIO
|
|
The BIO_ctrl_get_read_request() function returns the number of bytes that were last requested from bio by a BIO_read() operation. This is useful for BIO pairs, for example, so that the application kno... |
|
BIO_ctrl_get_write_guarantee(3) -- BIO pair BIO
|
|
The BIO_s_bio() function returns the method for a BIO pair. A BIO pair is a pair of source/sink BIOs where data written to either half of the pair is buffered and can be read from the other half. Both... |
|
BIO_ctrl_pending(3) -- Find out how many bytes are buffered in a BIO
|
|
The BIO_ctrl_pending() function returns the number of bytes buffered in a BIO. |
