FreeTDS Development Group

[Frediano Ziglio <freddy77 AT gmail.com>]

Perhaps this could explain the problem

http://www.gnu.org/software/gnutls/manual/html_node/On-Record-Padding.html

2011/6/28 Frediano Ziglio <freddy77 AT gmail.com>:
> 2011/6/28 Agnieszka Figiel <agnieszka AT llp.pl>:
>> 2011/6/28 Frediano Ziglio <freddy77 AT gmail.com>:
>>> 2011/6/28 Agnieszka Figiel <agnieszka AT llp.pl>:
>>>> The error encountered during tsql session error is as follows:
>>>>
>>>> Error 20004 (severity 9):
>>>>       Read from the server failed
>>>>       OS error 104, "Connection reset by peer"
>>>>
>>>
>>> I checked error 104 and is ECONNRESET (as string correctly reported).
>>> From log we send data and server refure it. Perhaps it does not like
>>> something in gnutls encoding :(
>>
>> You were right, apparently it works --with-openssl! That's really
>> great news, thank you!
>>
>> However, I'm still kind of confused about why it worked, maybe you
>> have a clue :) When we first started with freetds we used 0.82 from
>> Ubuntu package -- am I right that it comes compiled --with-openssl by
>> default? I'm quite certain it did not work for me at that time (same
>> db, same machine), I even posted about this to this list; problem was
>> resolved when I compiled --with-gnutls. So I guess 'something' must
>> have changed between the freetds versions that affected this -- just
>> curious if you have a guess what that could be?
>>
>> Thanks a lot!
>>
>
> It's a long story :)
>
> From 0.82 with some post patches we updated chipers. OpenSSL
> introduced a fix for a minor security issue which did not work with
> mssql so we find it and disable in order to make connection work. I
> don't know why GnuTLS does not work for you while OpenSSL but looking
> at your dump first 4096 (0x1000) bytes packet get encoded as a 0x1070
> data while second one (still 0x1000 bytes) get encoded as 0x10a0 bytes
> so I suppose it's something related to padding. I have to say that
> mssql is quite racist.
>
> Frediano Ziglio
>