3 ms·
I feel like this is an incorrect, inflammatory title. New integrations will cease to work with TLS < 1.2. Existing integrations are fine.
by snikch 8y ago
I feel like this is an incorrect, inflammatory title. New integrations will cease to work with TLS < 1.2. Existing integrations are fine.
- ryanisnan 8y agoAre you sure about that? It would appear that the library will raise an APIConnectionError, which may in turn do so based on the return code from Stripe's API.
- jetru 8y agoThis is a requirement for PCI. So I'm sure all integrations will cease to work with older TLS.
- fybe 8y agoNot necessarily as PCI requires a minimum of TLS 1.1 with 1.2 being the recommended. [0] [0]https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls https://blog.pcisecuritystandards.org/are-you-ready-for-30-j...
- habitue 8y agoNo, they are definitely shutting off all TLS less than 1.2, it's required to keep PCI certification.
- fybe 8y agoPCI requirements are TLS 1.1 minimum. Stripe's change is of course is due to PCI certification and 1.2 is strongly encouraged, but 1.2 is not the defacto version required. They could have just disabled 1.0 and keep 1.1. Just wanted to correct the info. (Also happy that they didn't take the minimum and took the extra effort to implement 1.2) Source: https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls https://blog.pcisecuritystandards.org/are-you-ready-for-30-j...