Closed AlBundy33 closed 9 months ago
The encryption setting does not apply to LOGIN. Login information has to be encrypted, and then the driver returns to unencrypted behavior after.
Here is a similar issue (https://github.com/microsoft/mssql-jdbc/issues/2214), which includes why this is something we can't really change.
ok - I was just curious🙂
not tested but I think setSSLProtocol("TLSv1")
in combination with re-enabled TLSv1 in java.security-file (jdk.tls.disabledAlgorithms) may avoid the exception.
JDBC-Driver 12.4.0 SQL Server: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 (Build 7600: )
-> I know it's very old. ;-)
Java-Version: 11
Even if encryption is disabled TDSChannel.enableSSL is called. 🤔
I also know that TLS1.2 would be better but I wonder why enableSSL is called if encryption is disabled.