with the registry to override the default behaviour.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Elie Lalo
Sent: Thursday, June 17, 2004 11:16 AM
To: [EMAIL PROTECTED]
Subject: Re: TLS and TOS
Mike,
I just wanted to let you know that I tried it on W2k Pro
This code is for UNIX.
I don't have an answer for Windows, but we are compiling the same code
from www.openssl.org
and I have to believe the TCP and SSL layer are separate and your
socket is going to behave
exactly like it use to.
Thanks,
Mike,
I just wanted to let you know that I tried it on W2k Pro and it works.
Thanks,
Elie
At 08:46 AM 6/17/2004 -0600, Mike Sontum wrote:
This code is for UNIX.
I don't have an answer for Windows, but we are compiling the same code
from www.openssl.org
and I have to believe the TCP and SSL layer
Of Elie Lalo
Sent: Thursday, June 17, 2004 11:16 AM
To: [EMAIL PROTECTED]
Subject: Re: TLS and TOS
Mike,
I just wanted to let you know that I tried it on W2k Pro and it works.
Thanks,
Elie
At 08:46 AM 6/17/2004 -0600, Mike Sontum wrote:
This code is for UNIX.
I don't have an answer
You can set any option you want for the socket.
I set the linger option. The SSL layer is above the TCP layer
and really does not affect the layer below it.
After you get your socket's accept or connect you can then do the
ssl = SSL_new (ctx);
/* sd is the socket */
SSL_set_fd (ssl, sd);
Hi Mike,
Does this work for Windows (I am writing my program on Windows platform,
and Windows presents a socket as a HANDLE )? It seems that this code is for
Unix.
Thanks,
Elie
At 04:31 PM 6/16/2004 -0600, Mike Sontum wrote:
You can set any option you want for the socket.
I set the linger
