TLS 1.2

Question

TLS 1.2

MonkAlex opened this issue 5 years ago · 6 comments

On February 19, 2020, Slack will end support for TLS versions 1.0 and 1.1. We've identified that one or more of your Slack apps are impacted by this change. If you don't upgrade your app to TLS 1.2, requests sent to any Slack endpoint will fail.
You must update your Slack app before February 21, 2020. Please verify which of your Slack apps are affected: https://api.slack.com/unsafe-tls-deprecation

In code i just use

      var client = new SlackConnector.SlackConnector();
      connect = await client.Connect(token);

have u apps in https://api.slack.com/unsafe-tls-deprecation or its only my problem?

Answer 1 · 2019-09-17T21:01:30.000Z

Thanks @MonkAlex - I need to investigate how nuget libraries can handle this as I believe the TLS handshake behaviour is handled in the execution context/host (e.g. console app)

Answer 2 · 2019-09-17T21:03:53.000Z

@MonkAlex as a stop gap, can you upgrade your app to be .NET 4.6.1 or above?

A solution for was to upgrade my application to the latest .NET framework: 4.6.1. In this framework version TLS 1.2 is a default cryptographic standard.

Answer 3 · 2019-09-18T05:31:01.000Z

@Workshop2 my app already 4.6.1, i try to update version to 4.7.2, its not help -- slack show my app on link.

Answer 4 · 2019-09-29T11:22:01.000Z

Set ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; on app start, but slack show my app on link...

No idea, how to fix it.

Answer 5 · 2019-10-04T08:25:26.000Z

Hmmm, nothing changed, but slack write on page now:
No action needed — we weren’t able to detect any legacy TLS usage.

Answer 6 · 2019-10-04T09:31:06.000Z

Good I know. I was able to replicate the bug.