If you are using OpenSSL then you must pass in the native sockets to the OpenSSL BIOs. The BIOs as they are called are the abstracted version of the I/O descriptor used to access the socket by the SSL library.
You are not going to get out of coding for the platform specific connection/listen, you still need WinSock and socket()/accept() calls. See the BIO_new_socket man page. Regards, Fred Crable > -----Original Message----- > From: Darren McDonald [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 9:38 AM > To: [EMAIL PROTECTED] > Subject: Re: normal vs openssl sockets > > > What I ment was when using ssl. > > >>> [EMAIL PROTECTED] 1/22/04 03:39:53 >>> > OpenSSL "sockets" are built on top of winsock, or whatever your native > > platform is. If you don't need SSL, etc., then just write > your code to > > use your local socket API directly. > /r$ > -- > Rich Salz, Chief Security Architect > DataPower Technology > http://www.datapower.com > > XS40 XML Security Gateway > http://www.datapower.com/products/xs40.html > > XML Security Overview > http://www.datapower.com/xmldev/xmlsecurity.html > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > > User Support Mailing List [EMAIL PROTECTED] > > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
