On Tue, Jun 28, 2005, Joe Santapau wrote:
> Thanks one and all,
>
> I had priviously used a socket BIO, but now I think I'll use accept() get
> what I need, and then populate it into a SSL * it might give me
> flexability
> with the socket itself, timeouts and the like.
>
You can stick to BIO
Thanks one and all,
I had priviously used a socket BIO, but now I think I'll use accept() get
what I need, and then populate it into a SSL * it might give me
flexability
with the socket itself, timeouts and the like.
Thanks,
Joe S.
_
PM
To: openssl-users@openssl.org
Subject: Re: Getting sockaddr_in structures from a BIO or SSL struct.
mclellan, dave wrote:
> Unless you have a specific reason to use BIOs, you can do a regular
accept()
Typical reason to use BIOs: Cross-platform portability. I recommend
using BIOs wheneve
mclellan, dave wrote:
Unless you have a specific reason to use BIOs, you can do a regular accept()
Typical reason to use BIOs: Cross-platform portability. I recommend
using BIOs whenever someone uses the pre-built Win32 OpenSSL
Installation Project binaries and they have difficulties.
Usi
PROTECTED] On Behalf Of Joe Santapau
Sent: Sunday, June 26, 2005 2:11 PM
To: openssl-users@openssl.org
Subject: Getting sockaddr_in structures from a BIO or SSL struct.
Hello All,
Is there a way in the OpenSSL API that allows you to save connection
information from a
BIO_do_accept() on a socket like
Hello All,
Is there a way in the OpenSSL API that allows you to save connection
information from a
BIO_do_accept() on a socket like accept() does ?, specifically a
sockaddr_in structure,
or similar.
If not, I am going to try to populate a BIO or SSL structure using
information from
a standar
