Re: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

2009-07-02 Thread Anil Tambe
Below is the trace .. (gdb) bt #0 sock_read (b=0x401a5880, out=0x40342820 "[Security]\n", outl=11) at bss_sock.c:143 #1 0xa30bf4 in BIO_read (b=0x401a5880, out=0x40342820, outl=11) at bio_lib.c:212 #2 0xa0cc1c in ssl23_read_bytes (s=0x4015e0b0, n=11) at s23_pkt.c:105 #3 0x9f0094 in ssl23_get_c

Re: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

2009-06-25 Thread Kyle Hamilton
Your server is requiring something akin to a STARTTLS, is my guess. Try telnetting to it and figuring out what it says before it expects the ClientHello. -Kyle H On Thu, Jun 25, 2009 at 8:40 AM, Anil Tambe wrote: > hi all, > > More debug on server side suggests that the problem is with the packet

Re: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

2009-06-25 Thread Anil Tambe
hi all, More debug on server side suggests that the problem is with the packet that is send to the ssl23_get_client_hello method 264 p=s->packet; (gdb) n 266 memcpy(buf,p,n); (gdb) print p $6 = (unsigned char *) 0x4033bc00 "[Security]\n\370"

Re: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

2009-06-24 Thread Anil Tambe
i guess in my case , server is not able to understand the client hello message .. any thoughts ? how do i debug it more .. On Thu, Jun 18, 2009 at 3:03 PM, Anil Tambe wrote: > Yes client is not able to connect and ssl23_get_client_hello is returning > -1 and so its going in > in s23_srvr.c . >

Re: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

2009-06-18 Thread Anil Tambe
Yes client is not able to connect and ssl23_get_client_hello is returning -1 and so its going in in s23_srvr.c . 568 if ((type < 1) || (type > 3)) (gdb) n 571 SSLerr(SSL_F_SSL23_GET_CLIENT_HELLO,SSL_R_UNKNOWN_PROTOCOL); (gdb) n 572 goto err; The value of type is 0

RE: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

2009-06-17 Thread David Schwartz
Anil Tambe wrote: > Getting the Below error : > error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol > As of now i am not able to reproduce the issue in stand alone openssl, > this is coming from the parent application which is consuming openssl. What is the problem? Are clients