Re: Compilation of openssl-0.9.8-stable-SNAP-20050624 fails on Solaris 2.5.1 x86

2005-06-26 Thread Andy Polyakov
I have another question on this build, config puts in -march=i486 but, shouldn't we be using -march=pentium The reason I ask is I see a lot of files that appear to be specific for the Pentium or later CPU - will these execute on a 80486? Yes, they will. -586 is legacy suffix and denotes

Getting sockaddr_in structures from a BIO or SSL struct.

2005-06-26 Thread Joe Santapau
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

RE: Compilation of openssl-0.9.8-stable-SNAP-20050624 fails on Solaris 2.5.1 x86

2005-06-26 Thread Ted Mittelstaedt
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andy Polyakov Sent: Sunday, June 26, 2005 9:35 AM To: openssl-dev@openssl.org Cc: openssl-users@openssl.org Subject: Re: Compilation of openssl-0.9.8-stable-SNAP-20050624 fails on Solaris 2.5.1 x86 I have

RE: Getting sockaddr_in structures from a BIO or SSL struct.

2005-06-26 Thread mclellan, dave
Unless you have a specific reason to use BIOs, you can do a regular accept() and use the socket and sockaddr_in from its return. Do whatever you want with the sockaddr_in. The socket returned by accept() is input to the SSL_set_fd to associate it with an SSL from SSL_new(). Then later, you

Re: Getting sockaddr_in structures from a BIO or SSL struct.

2005-06-26 Thread Thomas J. Hruska
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.