Re: SSL connection to MS SQL 2008
Plot Lost <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
Got a stage further with this: > The server is generating a error log entry of: > > 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. [CLIENT: 192.168.1.50] > 10/04/2010 12:00:37,Logon,Unknown,Error: 17835<c/> Severity: 20<c/> State: > 1. > Think this log entry is actually nothing to do with it, just happened to be in the logs at the same time... Doing some TCP monitoring showed the connection being dropped after the first packet in the SSL negotiation was sent, so as an experiment I change the list of available ciphers in tds_ssl_init in net.c - added just about every cipher I could think of and now the handshake does complete. It must of been trying to connect using a cipher other than one of the few normally listed in net.c, and that was causing the ssl handshake to fail. It now gets to the stage where the SSL is completed and the actual login packet is sent, but no response is recieved for that and it just hangs. I am now completely lost as to what else I can try to get this working...