RE: Enabling Logging in OpenSSL

2012-09-18 Thread Dave Thompson
From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Tuesday, 18 September, 2012 00:37 Hello Dave, Below is what i see in Server Logs Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed.

RE: Enabling Logging in OpenSSL

2012-09-17 Thread Dave Thompson
From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Friday, 14 September, 2012 20:53 On the issue i am working currently after i connect to a SQL Server, Client hello is sent successfully but I am not getting server hello and READ() below returns as highlighted. Looks like

Re: Enabling Logging in OpenSSL

2012-09-17 Thread Mithun Kumar
Hello Dave, Below is what i see in Server Logs Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library. Error: 17835, Severity: 20, State: 1 Do you have any pointers? Have you

Re: Enabling Logging in OpenSSL

2012-09-14 Thread Mithun Kumar
Hello Dave, On the issue i am working currently after i connect to a SQL Server, Client hello is sent successfully but I am not getting server hello and READ() below returns as highlighted. Looks like server is closing the connection after receiving a client hello. On the screen i see Socket

Re: Enabling Logging in OpenSSL

2012-09-11 Thread Mithun Kumar
Thanks Dave, Please find my reply inline. On Tue, Sep 11, 2012 at 8:08 AM, Dave Thompson dthomp...@prinpay.comwrote: From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Monday, 10 September, 2012 08:17 On Mon, Sep 10, 2012 at 1:52 PM, Dave Thompson dthomp...@prinpay.com

RE: Enabling Logging in OpenSSL

2012-09-11 Thread Dave Thompson
From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Tuesday, 11 September, 2012 02:10 On Tue, Sep 11, 2012 at 8:08 AM, Dave Thompson dthomp...@prinpay.com wrote: snip I didn't notice before, but 1433 on Windows is usually SQLServer. If so, SQLServer doesn't start

RE: Enabling Logging in OpenSSL

2012-09-10 Thread Dave Thompson
From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Monday, 10 September, 2012 01:56 Answering -users only, this isn't a -dev question. I have a challenge befor me where i have to debug a SSL handshake failure. Client has OpenSSL libraries and Server is Microsoft SQL Server.

Re: Enabling Logging in OpenSSL

2012-09-10 Thread Mithun Kumar
Hello Dave, Please find my reply inline On Mon, Sep 10, 2012 at 1:52 PM, Dave Thompson dthomp...@prinpay.comwrote: From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Monday, 10 September, 2012 01:56 Answering -users only, this isn't a -dev question. I have a challenge

RE: Enabling Logging in OpenSSL

2012-09-10 Thread Dave Thompson
From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar Sent: Monday, 10 September, 2012 08:17 On Mon, Sep 10, 2012 at 1:52 PM, Dave Thompson dthomp...@prinpay.com wrote: 2. If it's a handshake failure, can you use commandline s_client? That has logging builtin, use -msg

Enabling Logging in OpenSSL

2012-09-09 Thread Mithun Kumar
Hello All, I have a challenge befor me where i have to debug a SSL handshake failure. Client has OpenSSL libraries and Server is Microsoft SQL Server. I cant sniff the packets using WireShark nor can i enable server logs. All i can do i enable client logging. Any suggestions how to enable OpenSSL