cURL how to built in TLSv1.1 and TLSv1.2

Hi all, I am using WHMcs as automation tool and in the Health and system check it tells me that cURL reports that it does not support Secure TLSv1.1 and TLSv1.2, make sure an SSL Library that support TLS 1.1 and 1.2 is installed and supported by cURL. How would I get that in cURL builtin? I have asked on the WHMcs forum, but got only one comment and that was not very helpful. Currently using WHM 56 build 28 with cURL version 7.38.0 curl -V curl 7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz rpm -qa | grep openssl openssl-1.0.1e-48.el6_8.1.x86_64 openssl-devel-1.0.1e-48.el6_8.1.x86_64

array(9) {
  ["version_number">=>
  int(468480)
  ["age">=>
  int(3)
  ["features">=>
  int(34333)
  ["ssl_version_number">=>
  int(0)
  ["version">=>
  string(6) "7.38.0"
  ["host">=>
  string(24) "x86_64-unknown-linux-gnu"
  ["ssl_version">=>
  string(13) "OpenSSL/1.0.0"
  ["libz_version">=>
  string(5) "1.2.3"
  ["protocols">=>
  array(16) {
    [0]=>
    string(4) "dict"
    [1]=>
    string(4) "file"
    [2]=>
    string(3) "ftp"
    [3]=>
    string(4) "ftps"
    [4]=>
    string(6) "gopher"
    [5]=>
    string(4) "http"
    [6]=>
    string(5) "https"
    [7]=>
    string(4) "imap"
    [8]=>
    string(5) "imaps"
    [9]=>
    string(4) "pop3"
    [10]=>
    string(5) "pop3s"
    [11]=>
    string(4) "rtsp"
    [12]=>
    string(4) "smtp"
    [13]=>
    string(5) "smtps"
    [14]=>
    string(6) "telnet"
    [15]=>
    string(4) "tftp"
  }
}

Any help much appreciated.

cPanelMichael

August 03, 2016 15:36

Hello, You can review a manual workaround on a similar thread at: Update cPanel to TLS 1.2 without modifying system files [php5 + curlssl + apache2.4.x] Ensure you review the thread to verify it's what you are looking for before proceeding with that manual workaround. Thank you.

cURL how to built in TLSv1.1 and TLSv1.2

Comments

Didn't find what you were looking for?