Removing legacy support for TLS protocol versions 1.0 and 1.1

Updated on

On December 11, 2018 ScreenSteps will remove support for Transport Layer Security (TLS) protocol versions 1.0 and 1.1.

TLS is the protocol used when making secure connections to a website using the https:// url prefix.

Versions 1.0 and 1.1 have known security vulnerabilities and the best way to avoid those vulnerabilities is to not allow those versions to be used when making a secure connection to a website.

What do you need to do?

In most cases, nothing. Since all modern web browsers support TLS version 1.2, you and your customers probably won't even notice anything changed; however, if you or your customers happen to be using an older browser that doesn't support TLS 1.2, then you (and your end users) will need to update to a browser that does support it.

What is impacted?

Any secure connections (e.g. links starting with https://) made to the server will be impacted. This includes your public knowledge base, your ScreenSteps administration area, and any API requests.

Which browsers are supported going forward?

Anyone who will be using the ScreenSteps service will need to use a browser that supports TLS version 1.2. Here is a list of some browsers and when they started supporting TLS 1.2:

  • Google Chrome: 30+
  • Google Android OS Browser: Android 5.0+
  • Mozilla Firefox: 27+
  • Microsoft Internet Explorer: 11 (Can be enabled in 7+)
  • Microsoft Edge: 12+
  • Opera Browser: 17+
  • Apple Safari (desktop): 7+
  • Apple Safari (mobile): 5+

What if I have questions?

If you have any questions please email [email protected].

Previous Article WordPress integration is discontinued with version 4
Still Need Help? Contact Us