Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bio_push(3) [opendarwin man page]

BIO_push(3)							      OpenSSL							       BIO_push(3)

NAME
BIO_push, BIO_pop - add and remove BIOs from a chain. SYNOPSIS
#include <openssl/bio.h> BIO * BIO_push(BIO *b,BIO *append); BIO * BIO_pop(BIO *b); DESCRIPTION
The BIO_push() function appends the BIO append to b, it returns b. BIO_pop() removes the BIO b from a chain and returns the next BIO in the chain, or NULL if there is no next BIO. The removed BIO then becomes a single BIO with no association with the original chain, it can thus be freed or attached to a different chain. NOTES
The names of these functions are perhaps a little misleading. BIO_push() joins two BIO chains whereas BIO_pop() deletes a single BIO from a chain, the deleted BIO does not need to be at the end of a chain. The process of calling BIO_push() and BIO_pop() on a BIO may have additional consequences (a control call is made to the affected BIOs) any effects will be noted in the descriptions of individual BIOs. EXAMPLES
For these examples suppose md1 and md2 are digest BIOs, b64 is a base64 BIO and f is a file BIO. If the call: BIO_push(b64, f); is made then the new chain will be b64-chain. After making the calls BIO_push(md2, b64); BIO_push(md1, md2); the new chain is md1-md2-b64-f. Data written to md1 will be digested by md1 and md2, base64 encoded and written to f. It should be noted that reading causes data to pass in the reverse direction, that is data is read from f, base64 decoded and digested by md1 and md2. If the call: BIO_pop(md2); The call will return b64 and the new chain will be md1-b64-f data can be written to md1 as before. RETURN VALUES
BIO_push() returns the end of the chain, b. BIO_pop() returns the next BIO in the chain, or NULL if there is no next BIO. SEE ALSO
TBA 0.9.7d 2002-04-30 BIO_push(3)

Check Out this Related Man Page

BIO_push(3)							      OpenSSL							       BIO_push(3)

NAME
BIO_push, BIO_pop - add and remove BIOs from a chain. SYNOPSIS
#include <openssl/bio.h> BIO * BIO_push(BIO *b,BIO *append); BIO * BIO_pop(BIO *b); DESCRIPTION
The BIO_push() function appends the BIO append to b, it returns b. BIO_pop() removes the BIO b from a chain and returns the next BIO in the chain, or NULL if there is no next BIO. The removed BIO then becomes a single BIO with no association with the original chain, it can thus be freed or attached to a different chain. NOTES
The names of these functions are perhaps a little misleading. BIO_push() joins two BIO chains whereas BIO_pop() deletes a single BIO from a chain, the deleted BIO does not need to be at the end of a chain. The process of calling BIO_push() and BIO_pop() on a BIO may have additional consequences (a control call is made to the affected BIOs) any effects will be noted in the descriptions of individual BIOs. EXAMPLES
For these examples suppose md1 and md2 are digest BIOs, b64 is a base64 BIO and f is a file BIO. If the call: BIO_push(b64, f); is made then the new chain will be b64-chain. After making the calls BIO_push(md2, b64); BIO_push(md1, md2); the new chain is md1-md2-b64-f. Data written to md1 will be digested by md1 and md2, base64 encoded and written to f. It should be noted that reading causes data to pass in the reverse direction, that is data is read from f, base64 decoded and digested by md1 and md2. If the call: BIO_pop(md2); The call will return b64 and the new chain will be md1-b64-f data can be written to md1 as before. RETURN VALUES
BIO_push() returns the end of the chain, b. BIO_pop() returns the next BIO in the chain, or NULL if there is no next BIO. SEE ALSO
TBA 50 2013-03-05 BIO_push(3)
Man Page

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Grep Command

I am using the first example below to grep a string that has the IP of 249.185.xx and then the text BIO later in the string. This is working, but when I try to use the 2nd example and add a search for any string containing the text NodeStatus it is grepping all IPs and not just the 249.185 IPs. ... (1 Reply)
Discussion started by: robertson1995
1 Replies

2. Solaris

iostat command question

Iostat inquiry;# iostat -e ---- errors --- device s/w h/w trn tot fd0 0 0 0 0 md0 0 0 0 0 md1 0 0 0 0 md2 0 0 0 0 md10 0 0 0 0 md11 0 0 0 0 md12 0 0 0 0 md30 0 0 0 0 md31 0 0 0 0 md32 0 0 0 0 md40 0 0 0 0 md41 0 0 0 0 md42 0 0 0 0 md50 0 0 0 0 md51 0 0 0 0 md52 0 0 0 0 md60 0 0 0... (2 Replies)
Discussion started by: pepi
2 Replies

3. Filesystems, Disks and Memory

MDADM Failure - where it came from?

Hello, i have a system with 6 sata3 seagate st3000dm01 disks running on stable Debian with software raid mdadm. i have md0 for root and md1 for swap and md2 for the files. i now want to add one more disk = sdh4 for md2 but i got this errors: The new disk is connected to an 4 port sata... (7 Replies)
Discussion started by: Sunghost
7 Replies

4. Shell Programming and Scripting

How to reverse the b64 format(encoded b64(b64(md5($pass)))) into md5 hash format?

I have about 1500 rows (encoded b64(b64(md5($pass))) algorythm) in a file. I would like reverse the b64 into md5 hash format. How could I do that from command line? So I need only the correct md5 hash formats. These row format: 4G5qc2WQzGES6QkWAUgl5w P9tKxonBOg3ymr8vOBLnDA... (1 Reply)
Discussion started by: freeroute
1 Replies