On Thu, May 28, 2009 at 3:32 PM, Victor Duchovni
wrote:
> NO! You call
>
> n = SSL_write(myssl, buffer, len);
> err = SSL_get_error(myssl, n);
>
> "err" may be SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE, in which case
> you must retry the write again later, after there is room.
>
>
On Tue, May 26, 2009 at 5:27 PM, Victor Duchovni
wrote:
> On Tue, May 26, 2009 at 05:02:59PM -0400, Aaron Wiebe wrote:
>
>> >> You're looking for a BIO_s_mem.
>> >
>> > No, he is looking for BIO_new_bio_pair(3) and SSL_set_bio(3).
So, apologies for ha
On Tue, May 26, 2009 at 4:46 PM, Victor Duchovni
wrote:
> On Tue, May 26, 2009 at 01:13:33PM -0700, Kyle Hamilton wrote:
>
>> You're looking for a BIO_s_mem.
>
> No, he is looking for BIO_new_bio_pair(3) and SSL_set_bio(3).
And this is where I'm running into confusing bits of information.
Bluntly
Greetings All,
I've gone through various levels of documentation to see if there is a
method available to implement SSL as I have envisioned, but I haven't
been able to find what I'm looking for. Perhaps someone here could
point me in a good direction...
I'm developing a nonblocking application
