You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi we recently ran into an issue where EF6.exe (used visual studio package manager) would fail to update databases which ran encrypted connection with TLS 1.2 as the minimum requirement.
Changing our DbConfiguration to include System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
Provides a workaround for the problem. But I would prefer not having a change of SecurityProtocols change present in order to use EF.
Checking the csproj shows it targeting .NET Framework 4.5 as the highest. From memory this means it will only allow SSLv3, TLS 1.0 and TLS 1.1.
The text was updated successfully, but these errors were encountered:
This issue has been closed because EF6 is no longer being actively developed. We are instead focusing on stability of the codebase, which means we will only make changes to address security issues. See the repo README for more information.
Hi we recently ran into an issue where EF6.exe (used visual studio package manager) would fail to update databases which ran encrypted connection with TLS 1.2 as the minimum requirement.
Changing our DbConfiguration to include
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
Provides a workaround for the problem. But I would prefer not having a change of SecurityProtocols change present in order to use EF.
Checking the csproj shows it targeting .NET Framework 4.5 as the highest. From memory this means it will only allow SSLv3, TLS 1.0 and TLS 1.1.
The text was updated successfully, but these errors were encountered: