[EMAIL PROTECTED] writes:
> When SSL_connect is tried to a port where TCP process is listening,
> how SSL client comes to know that the port it is trying is not TLS process
> but a TCP process.
That's layer confusion. TLS runs on top of TCP.
> how should this problem be solved.
>
> Our observation:
> SSL_connect to a TCP process is blocked indefinitely.
What happens depends on what protocol is being run on the port
you're connecting to. Some protocol implementations will throw
errors, some won't. There's no general way to solve this
problem from the client side. Consider what happens if there
is a protocol which uses the first four bytes of the packet
as the length of the remaining data. Such a protocol will
block indefinitely when handed an SSL client hello.
All the client can do in this case is time out.
-Ekr
--
[Eric Rescorla [EMAIL PROTECTED]]
http://www.rtfm.com/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
