I would like to Thank you Stephen. That was exactly what I was looking for.
> Thank you for you help, Dr Stephen Henson. I have another question for
> everyone though. Windows doesn't necessarily seem to work with file
> descriptors. How should I treat them if Windows doesn't have it? What is
> re
On Thu, Sep 13, 2007, Loukas Stoumbos wrote:
> Thank you for you help, Dr Stephen Henson. I have another question for
> everyone though. Windows doesn't necessarily seem to work with file
> descriptors. How should I treat them if Windows doesn't have it? What is
> returned instead on a windows mac
om: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dr. Stephen Henson
Sent: Thursday, September 13, 2007 8:14 PM
To: openssl-users@openssl.org
Subject: Re: Windows and file descriptors
On Thu, Sep 13, 2007, Loukas Stoumbos wrote:
>
>
> I appreciate the reply but perhaps someone can p
On Thu, Sep 13, 2007, Loukas Stoumbos wrote:
>
>
> I appreciate the reply but perhaps someone can provide some insight. Looking
> at the man page it says this.
>
> BIO_set_nbio() sets the non blocking I/O flag to n. If n is zero then
> blocking I/O is set. If n is 1 then non blocking I/O is set
I appreciate the reply but perhaps someone can provide some insight. Looking
at the man page it says this.
BIO_set_nbio() sets the non blocking I/O flag to n. If n is zero then
blocking I/O is set. If n is 1 then non blocking I/O is set. Blocking I/O is
the default. The call to BIO_set_nbio() sh
Hello,
> I am looking for a way to convert this segment of code. It’s probably
> not right but here is the question. How would I retrieve the socket
> pointer from OpenSSL. Does OpenSSL even provide this? Also what does
> OpenSSL provide as a return from function SSL_get_fd when using
> Windows?
>
