Re: [openssl-users] Questions on internal-buffers being used

2016-10-14 Thread Benjamin Kaduk
Showing the contents of the error queue would help, but it seems most likely that what is going on is that I overlooked the fact that BIO_new_mem_buf() makes a read-only BIO. I'm not sure offhand that there's a way to get a writeable BIO using application-supplied buffers; maybe someone else on

Re: [openssl-users] Questions on internal-buffers being used

2016-10-13 Thread Ajay Garg
Thanks Ben for the reply. I tried the following, and the code hits the block as commented :: ### static char inter_bio_buf[1000]; static char network_bio_buf[1000]; { BIO *inter_bio_buf_bio = NULL,

Re: [openssl-users] Questions on internal-buffers being used

2016-10-11 Thread Benjamin Kaduk
On 10/11/2016 02:06 PM, Ajay Garg wrote: > Hi All. > > > a) > In the call, > int BIO_new_bio_pair(BIO **bio1, size_t writebuf1, BIO **bio2, size_t > writebuf2); are internal-buffers malloc'ed for each of "bio1" and "bio2"? > If yes, is there a way to pass buffers from the application-layer? I >