4 ms·
> If you care about ancient clients, you should be using SHA-1 still I want to point out here that the oldest OS the newest Firefox supports is Windows XP SP2
by tinalumfoil 10y ago
> If you care about ancient clients, you should be using SHA-1 still
I want to point out here that the oldest OS the newest Firefox supports is Windows XP SP2 [0], released 8 years ago, and a free upgrade from the original XP release 14 years ago. Unless you need support for last millennium's hardware you have no excuse for not supporting SHA-256.
[0] https://en.wikipedia.org/wiki/Firefox#System_requirements https://en.wikipedia.org/wiki/Firefox#System_requirements
- toast0 10y agoNote that I contrasted modern browsers and ancient clients. Client libraries in shipped devices tend to be several years behind state of the art when they were shipped, and live in the field without updates. As an example Symbian didn't ship SHA-256 support in their 9.3 release from 2006, but Firefox shipped support in their 1.0 release from 2004. Whenever TLS 1.0 starts getting pulled from servers, it's going to be similarly painful. Nokia S40/Asha (last device released in 2014), only supports TLS 1.0, even though TLS 1.2 was 6 years old at that point. Nobody meaningfully supports TLS 1.1, but not TLS 1.2, so let's not hold lack of TLS 1.1 support against them. (Not to pick on Nokia, they just happen to be an easily identifiable client platform that I'm familiar with)