Skip to content
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.

TLS 1.0/1.1 plan #11

Closed
JakeChampion opened this issue Oct 2, 2017 · 4 comments
Closed

TLS 1.0/1.1 plan #11

JakeChampion opened this issue Oct 2, 2017 · 4 comments

Comments

@JakeChampion
Copy link

Hi,

I see you are using the legacy TLS 1.1/1.0 and 3DES certificate from Fastly. Do you have any plans for when Fastly remove legacy TLS 1.1/1.0 and 3DES support in June 2018?

@jimaek
Copy link
Member

jimaek commented Oct 2, 2017

I will need to get in contact with them to make sure. Do you require the older TLS versions for some use-case?

@JakeChampion
Copy link
Author

Yes, I support IE 10 and Android 4 which do not work with TLS 1.2. I was wondering if it is possible to switch provider based on TLS support using Cedexis, that could be a solution.

@jimaek
Copy link
Member

jimaek commented Oct 2, 2017

The code runs on the DNS level so it doesn't have access to this kind of information.
We have 2 options here:

  1. Work with Fastly to somehow continue the support of older TLS. I will email them today.
  2. Exclude Fastly from serving to countries with high IE usage levels. Not perfect but it should solve most problems.

@jimaek
Copy link
Member

jimaek commented Oct 16, 2017

I finally got a response from them. They said its not possible.
I am thinking about possible solution because I know Algolia also relies on the older TLS support.

I will need to talk to them but I am thinking at best disabling Fastly for countries like India where old IE is popular and at worse removing them completely.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants