Nevermind. I didn't realize that I did have the call in there for my socket connect() (which was in another part of the code for non-ssl connections...it is needed for both). I had though SSL_connect took care of that too.
On Sun, Oct 14, 2012 at 5:35 PM, Derek Cole <derek.c...@gmail.com> wrote: > Hello, > > I am trying to use SSL_connect. I have bound a socket to my interface, set > up the context, and call SSL_connect(). This is returning a -1, which I > catch, and call SSL_get_error() to fall through a switch statement. It is > retuning a SSL_ERROR_WANT_WRITE > > So I am trying to use pselect in a while loop here to get the return. I > call SSL_get_fd() to get the file descriptor, FD_SET() to add to my fd_set, > and then pselect(ssl_fd+1, 0, &fds, 0, &timeout, NULL) > > This reaches my timeout every time. Is there a reason to see why it is not > connecting, even though the intiial SSL_connect returned WANT_WRITE? > > Just to complete the model of what I was doing - assuming there was a > succesful pselect(), I was going to call SSL_connect() again, and either go > through the loop again, or exitand continue. >
