add tlsmin connection parameter

[shueybubbles]

Fixes #33
Adds tlsmin parameter to the connection string to enable use of 1.0 and 1.1 as needed.

[codecov-commenter]

Codecov Report

Merging #45 (5f09ec8) into main (c33ed63) will increase coverage by 0.10%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #45      +/-   ##
==========================================
+ Coverage   72.03%   72.14%   +0.10%     
==========================================
  Files          23       23              
  Lines        5604     5604              
==========================================
+ Hits         4037     4043       +6     
+ Misses       1319     1314       -5     
+ Partials      248      247       -1     

Impacted Files	Coverage Δ
tds.go	71.78% <0.00%> (+0.64%)	⬆️
token.go	64.44% <0.00%> (-0.44%)	⬇️
mssql.go	85.78% <0.00%> (+0.34%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us.

[apoorvdeshmukh]

Looks Good

[efjoubert]

I am just adding this comment here
This will resolve the issue

Just change the code at the beginning in SetupTLS to

config := tls.Config{
ServerName: hostInCertificate,
InsecureSkipVerify: insecureSkipVerify,

// fix for https://github.com/microsoft/go-mssqldb/issues/166
// Go implementation of TLS payload size heuristic algorithm splits single TDS package to multiple TCP segments,
// while SQL Server seems to expect one TCP segment per encrypted TDS package.
// Setting DynamicRecordSizingDisabled to true disables that algorithm and uses 16384 bytes per TLS package
DynamicRecordSizingDisabled: true,
MinVersion:                  tls.VersionTLS10, //this is added

}

[shueybubbles]

I am just adding this comment here This will resolve the issue

Just change the code at the beginning in SetupTLS to

config := tls.Config{ ServerName: hostInCertificate, InsecureSkipVerify: insecureSkipVerify,

// fix for https://github.com/microsoft/go-mssqldb/issues/166
// Go implementation of TLS payload size heuristic algorithm splits single TDS package to multiple TCP segments,
// while SQL Server seems to expect one TCP segment per encrypted TDS package.
// Setting DynamicRecordSizingDisabled to true disables that algorithm and uses 16384 bytes per TLS package
DynamicRecordSizingDisabled: true,
MinVersion:                  tls.VersionTLS10, //this is added

}

I don't think the goal is to make 1.0 the default all the time, as it's not secure.