"Fossies" - the Fresh Open Source Software Archive

Member "openssl-1.0.2q/doc/crypto/BIO_f_base64.pod" (20 Nov 2018, 1923 Bytes) of package /linux/misc/openssl-1.0.2q.tar.gz:

Caution: As a special service "Fossies" has tried to format the requested pod source page into HTML format but links to other pod pages may be missing or even errorneous. Alternatively you can here view or download the uninterpreted pod source code. A member file download can also be achieved by clicking within a package contents listing on the according byte size field. See also the last Fossies "Diffs" side-by-side code changes report for "BIO_f_base64.pod": 1.1.0g_vs_1.1.1-pre2.


BIO_f_base64 - base64 BIO filter


 #include <openssl/bio.h>
 #include <openssl/evp.h>

 BIO_METHOD *   BIO_f_base64(void);


BIO_f_base64() returns the base64 BIO method. This is a filter BIO that base64 encodes any data written through it and decodes any data read through it.

Base64 BIOs do not support BIO_gets() or BIO_puts().

BIO_flush() on a base64 BIO that is being written through is used to signal that no more data is to be encoded: this is used to flush the final block through the BIO.

The flag BIO_FLAGS_BASE64_NO_NL can be set with BIO_set_flags() to encode the data all on one line or expect the data to be all on one line.


Because of the format of base64 encoding the end of the encoded block cannot always be reliably determined.


BIO_f_base64() returns the base64 BIO method.


Base64 encode the string "Hello World\n" and write the result to standard output:

 BIO *bio, *b64;
 char message[] = "Hello World \n";

 b64 = BIO_new(BIO_f_base64());
 bio = BIO_new_fp(stdout, BIO_NOCLOSE);
 BIO_push(b64, bio);
 BIO_write(b64, message, strlen(message));


Read Base64 encoded data from standard input and write the decoded data to standard output:

 BIO *bio, *b64, *bio_out;
 char inbuf[512];
 int inlen;

 b64 = BIO_new(BIO_f_base64());
 bio = BIO_new_fp(stdin, BIO_NOCLOSE);
 bio_out = BIO_new_fp(stdout, BIO_NOCLOSE);
 BIO_push(b64, bio);
 while((inlen = BIO_read(b64, inbuf, 512)) > 0) 
        BIO_write(bio_out, inbuf, inlen);



The ambiguity of EOF in base64 encoded data can cause additional data following the base64 encoded block to be misinterpreted.

There should be some way of specifying a test that the BIO can perform to reliably determine EOF (for example a MIME boundary).