4 ms·
I assure you the browsers were not quick to disable TLS 1.0. They've dragged down their feet as long as they could and beyond. TLS 1.0 and previous protocols h
by user5994461 7y ago
I assure you the browsers were not quick to disable TLS 1.0. They've dragged down their feet as long as they could and beyond.
TLS 1.0 and previous protocols have been prohibited from usage since around 2017 by PCI DSS and most regulations. Any company that gets a basic security audit or self-submit their website to https://www.ssllabs.com/ssltest/ https://www.ssllabs.com/ssltest/ would have been red flagged for using TLS 1.0 for years.
I've worked on the TLS upgrade in some financial institutions that notoriously always lag behind and even them have been ready for a while.
At this stage websites stuck on TLS 1.0 are either unmaintained for years or purposefully trying to support a Windows XP and Java 7 audience.
- psadauskas 7y ago> At this stage websites stuck on TLS 1.0 are either unmaintained for years or purposefully trying to support a Windows XP and Java 7 audience. Or are using Heroku Automated Certificate Management https://help.heroku.com/G0YVUNPG/how-do-i-disable-support-for-tls-1-0-or-1-1-on-a-heroku-app https://help.heroku.com/G0YVUNPG/how-do-i-disable-support-fo...
- 43920 7y agoAs long as you support 1.2 as well (which Heroku does), you're fine; this is about sites that _only_ support 1.0 or 1.1.
- deleted 7y ago[deleted]