From October 17th the weak cipher suits for TLS 1.2 will be disabled, see screenshot about changes that are currently in sod/stage and will be implemented in production.
Please make sure your integrations, connectors, db mirroring instances still continue to operate normally.
Best regards.
All Replies (3)
For others reading along, the 2 cipher suites for TLS 1.2 that are still supported after the 17th (TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) are supported on Windows server 2016 and higher.
So if you or a customer is still running Windows server 2012 R2 (or lower...), that will be an issue.
Hi, we are one of those customers with a Windows 2012R2 Server...
Unfortunately we missed this update.
I read that besides migrating or upgrading to 2016 its possible to setup a proxy to receive our calls and forward them to Superoffice and vice versa. Does anyone have any practical experience with this or have an idea about the feasibility?
Regards
I'll try to run proxy today in our production. I've done some tests locally and it worked fine. I've used Yarp.ReverseProxy package in .NET 8 to build it. It is extremely simple .NET project.
Every big company (Facebook, Amazon, Google, Microsoft) supports Windows 2012 R2 ciphers.