[wp-trac] [WordPress Trac] #34924: Network upgrade fails on tls 1.2 only servers

WordPress Trac noreply at wordpress.org
Tue Mar 29 07:09:57 UTC 2016

#34924: Network upgrade fails on tls 1.2 only servers
 Reporter:  mensmaximus         |       Owner:
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  HTTP API            |     Version:  2.7
 Severity:  normal              |  Resolution:
 Keywords:  https dev-feedback  |     Focuses:  multisite

Comment (by mensmaximus):

 Replying to [comment:12 dd32]:
 >  * in the cURL transport - attempt to use the most-popular SSL standard,
 in the event a `SSL Connect` failure is hit, attempt others in a fallback
 case. cURL not being able to negotiate a secure connection is a big enough
 bug to warrant a workaround

 cURL is able to negotiate. Please reread my postings: "setting
 CURLOPT_SSLVERSION to CURL_SSLVERSION_TLSv1 because it will auto-negotiate
 between all available TLS versions and choose the highest available"

 To fix this TLS/SSL issue in WordPress simply set CURLOPT_SSLVERSION to
 CURL_SSLVERSION_TLSv1 instead of omitting this parameter at all as you do
 right now in WordPress. There is no need to implement a fallback that is
 already built in to cURL.

Ticket URL: <https://core.trac.wordpress.org/ticket/34924#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list