In #458, code was added to try TlsVersions.None first, then fall back to TLS 1.1 if that failed. This was done to accommodate yaSSL-based servers (MySQL <= 5.7.28).
This has caused multiple problems over the years:
In addition, it makes debugging TLS connection issues harder:
Since this fix was only for a major version of MySQL Server that is no longer supported (5.7), there are minor versions that don't have the problem (>= 5.7.28), TLS 1.1 should generally be avoided, and there's now a Tls Versions connection string option that could be used as a workaround, the fallback code should simply be deleted and affected users advised to use the connection string setting.
In #458, code was added to try
TlsVersions.Nonefirst, then fall back to TLS 1.1 if that failed. This was done to accommodate yaSSL-based servers (MySQL <= 5.7.28).This has caused multiple problems over the years:
The collection already contains item with same key 'net.transport'exception #1405In addition, it makes debugging TLS connection issues harder:
Since this fix was only for a major version of MySQL Server that is no longer supported (5.7), there are minor versions that don't have the problem (>= 5.7.28), TLS 1.1 should generally be avoided, and there's now a
Tls Versionsconnection string option that could be used as a workaround, the fallback code should simply be deleted and affected users advised to use the connection string setting.