Hi, we have to use TLS1.2 for all communication.
We are using the SLES 11 Security Module https://www.suse.com/documentation/suse-best- practices/singlehtml/securitymodule/securitymodule.html to enable TLS1.2 in our SMT server and installed the openssl und curl versions from this module on our SLES 11 SP4 server.
Everything is working fine, except zypper.
curl can connect to the SMT server with TLS1.2, but zypper not…
Looks like zypper is using the libcurl and not curl.
Is there any way to get zypper to use a newer version of the libcurl library?
On 05/18/2018 07:44 AM, vockinger wrote:[color=blue]
Hi, we have to use TLS1.2 for all communication.
We are using the SLES 11 Security Module https://www.suse.com/documentation/suse-best-
practices/singlehtml/securitymodule/securitymodule.html to enable TLS1.2
in our SMT server and installed the openssl und curl versions from this
module on our SLES 11 SP4 server.
Everything is working fine, except zypper.
curl can connect to the SMT server with TLS1.2, but zypper not…
Looks like zypper is using the libcurl and not curl.[/color]
Most programs do not use ‘curl’ directly, but use libcurl, so that’s
pretty normal.
Which version of libcurl do you have? I thought the security module came
with a new version of libcurl as well as curl. A week ago I was on a
system that had the security module to work on a certificate trust issue,
and in that case the client was just ‘curl’, but other things worked.
What do you see from this:
zypper lr -u
zypper se curl #should also see libcurl packages
[color=blue]
Is there any way to get zypper to use a newer version of the libcurl
library?[/color]