Changes between Initial Version and Version 1 of Ticket #36320, comment 18
- Timestamp:
- 03/30/2016 12:13:22 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36320, comment 18
initial v1 41 41 The most reliable way around this that I can envision is to somehow re-implement TLS 1.2 in php to make WordPress independent of OpenSSL and/or cURL. Since we cannot know what the status of OpenSSL or cURL is on any particular host, the only reliable solution is to DIY. Not sure how to achieve this, or if it would even be possible, but it is the right way as I see it. fsockopen() depends on OpenSSL for tls, so that's out... 42 42 43 PHP sockets might be workable, but again, we cannot know if any particular host as built php with --enable-sockets.43 PHP sockets might be workable, but again, we cannot know if any particular host has built php with --enable-sockets. 44 44 45 45 I'll dig around a bit and see if it might be possible to create a host independent TLS 1.2 solution for php.