Essentially, lets say I have a file descriptor(int) for an existing
SOCKS connection. I want SSL to use that existing file descriptor and
to know that it doesn't need to open the actual TCP/IP connection.
What are the BIO and such calls for this? Currently I'm using
BIO_new_ssl_connect and
I am using BIO_set_fd to set the file descriptor of a BIO created by
BIO_new_connect to the socket of an existing SOCKS connection. This
seems to work fine, lsof -i reports that indeed I am connected to the
proxy. However, I want to be sure that my ip address is not embedded
in the SSL
On Wed, Mar 02, 2005, Peter wrote:
I am using BIO_set_fd to set the file descriptor of a BIO created by
BIO_new_connect to the socket of an existing SOCKS connection. This
seems to work fine, lsof -i reports that indeed I am connected to the
proxy. However, I want to be sure that my ip
Hi,
I'm curious about SSLs behavior over a SOCKS connection. I would
assume that it would function fine, but that the SSL client certificate
passed would contain the inner ip address of the network behind the
SOCKS proxy. Is there anyway to setup an SSL connection in a way so
that the
