skoltogyan Absent Member.
Absent Member.
11245 views

NCC and curl: (60) SSL certificate problem, verify that the

Server:
Server: OES2SP2 (i386 with GW8.0.2HP2)

From the server GUI i do:
1) YaST2 Control Center
2) Novell Customer Center Configuration
[+] Registration code
Press "Next"

and after some time i have this error:
"
Execute curl command failed with '60':
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: cURL - Details on Server SSL Certificates

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). The default
bundle is named curl-ca-bundle.crt; you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
"

At this time i the /var/log/warn i see:
..
Jan 14 16:14:56 ercog suse_register[26940]: Commandline params: no-optional:0 forceregistration:1 no-hw-data:0 batch:0
Jan 14 16:14:56 ercog suse_register[26940]: Argument Dump: $VAR1 = { 'timezone' => { 'kind' => 'mandatory', 'value' => 'Europe/Kiev', 'flag' => 'i' }, 'processor' => { 'kind' => 'mandatory', 'value' => 'i686', 'flag' => 'i' }, 'platform' => { 'kind' => 'mandatory', 'value' => 'i386', 'flag' => 'i' } };
Jan 14 16:14:56 ercog suse_register[26940]: Products Dump: $VAR1 = [];
Jan 14 16:14:56 ercog suse_register[26940]: Execute curl command failed with '60': curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: cURL - Details on Server SSL Certificates curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). The default bundle is named curl-ca-bundle.crt; you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. (4)
Jan 14 16:14:56 ercog suse_register[26940]: Execute curl command failed with '60': curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: cURL - Details on Server SSL Certificates curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). The default bundle is named curl-ca-bundle.crt; you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. (4)
Jan 14 16:14:56 ercog suse_register[26940]: Commandline params: no-optional:0 forceregistration:1 no-hw-data:0 batch:0
Jan 14 16:14:56 ercog suse_register[26940]: Argument Dump: $VAR1 = { 'timezone' => { 'kind' => 'mandatory', 'value' => 'Europe/Kiev', 'flag' => 'i' }, 'processor' => { 'kind' => 'mandatory', 'value' => 'i686', 'flag' => 'i' }, 'platform' => { 'kind' => 'mandatory', 'value' => 'i386', 'flag' => 'i' } };
Jan 14 16:14:56 ercog suse_register[26940]: Products Dump: $VAR1 = [];
Jan 14 16:14:56 ercog suse_register[26940]: Execute curl command failed with '60': curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: cURL - Details on Server SSL Certificates curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). The default bundle is named curl-ca-bundle.crt; you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA representedthe bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. (4)
Jan 14 16:14:56 ercog suse_register[26940]: Commandline params: no-optional:0 forceregistration:1 no-hw-data:0 batch:0
Jan 14 16:14:56 ercog suse_register[26940]: Argument Dump: $VAR1 = { 'timezone' => { 'kind' => 'mandatory', 'value' => 'Europe/Kiev', 'flag' => 'i' }, 'processor' => { 'kind' => 'mandatory', 'value' => 'i686', 'flag' => 'i' }, 'platform' => { 'kind' => 'mandatory', 'value' => 'i386', 'flag' => 'i' } };
Jan 14 16:14:56 ercog suse_register[26940]: Products Dump: $VAR1 = [];
Jan 14 16:14:56 ercog suse_register[26940]: Execute curl command failed with '60': curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: cURL - Details on Server SSL Certificates curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). The default bundle is named curl-ca-bundle.crt; you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. (4)
--------------------

On the server correct time is established ( Jan 14 16:14 )
This TID 3963765 - hasn't helped

Please, Help me.

Serg
Labels (2)
0 Likes
7 Replies
Knowledge Partner
Knowledge Partner

Re: NCC and curl: (60) SSL certificate problem, verify that the

Hi.

This is a current problem wit NCC.

To fix it:

Go into Yast, Software Management, and install the openssl-certs package.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
skoltogyan Absent Member.
Absent Member.

Re: NCC and curl: (60) SSL certificate problem, verify that

In The YaST (oes2sp2) i see only:
[ + ] compat-openssl097g
[ ] novell-encrypt
[ + ] openssl
[ ] openssl-devel
[ ] openssl-doc
[ ] openssl-ibmca
[ ] php5-openssl
[ ] python-openssl

where:
[ + ] - installed
[ ] - available

Serg
0 Likes
skoltogyan Absent Member.
Absent Member.

Re: NCC and curl: (60) SSL certificate problem, verify that

Found and downlaod from the Novell: Downloads.
Thank your. !

Serg
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NCC and curl: (60) SSL certificate problem, verify that the

I'm having this same problem and can't find it on Novell's site. Can you
provide a link or what search terms you used?




>>>

From: skoltogyan<skoltogyan@no-mx.forums.novell.com>
To: novell.support.open-enterprise-server.linux.administration
Date: 1/14/2012 1:26 PM
Subject: Re: NCC and curl: (60) SSL certificate problem, verify that the


Found and downlaod from the 'Novell: Downloads'
(http://www.novell.com/downloads).
Thank your. !

Serg


‑‑
skoltogyan
‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â€
‘‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
skoltogyan's Profile: http://forums.novell.com/member.php?userid=9261
View this thread: http://forums.novell.com/showthread.php?t=450735



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NCC and curl: (60) SSL certificate problem, verify that the

Aha! With Googling, I was able to find it on Novell's site. Does anyone
else still miss the old support site before it was revamped 4 or 5 years
ago?

Anyway, here's the TID:
http://www.novell.com/support/dynamickc.do?cmd=show&forward=nonthreadedKC&do
cType=kc&externalId=7008662&sliceId=1

and a link to the download page (which is also in the TID:
http://download.novell.com/protected/Summary.jsp?buildid=_7Pup8oi5zw~

And some search terms Google will catch:
This resolved my issues with curl error 60 and download patches from Novell.
I don't have an SMT server. Installing the openssl-certs package resolved
the issue.




>>>

From: T. Bowman<tbowman@umphysicians.REMOVEumnTHIS.edu>
To: novell.support.open-enterprise-server.linux.administration
Date: 1/18/2012 7:57 AM
Subject: Re: NCC and curl: (60) SSL certificate problem, verify that the

I'm having this same problem and can't find it on Novell's site. Can you
provide a link or what search terms you used?




>>>

From: skoltogyan<skoltogyan@no‑mx.forums.novell.com>
To: novell.support.open‑enterprise‑server.linux.administration
Date: 1/14/2012 1:26 PM
Subject: Re: NCC and curl: (60) SSL certificate problem, verify that the


Found and downlaod from the 'Novell: Downloads'
(http://www.novell.com/downloads).
Thank your. !

Serg


‑‑
skoltogyan
‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑Ã
¢
*‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑*
‘‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
skoltogyan's Profile: http://forums.novell.com/member.php?userid=9261
View this thread: http://forums.novell.com/showthread.php?t=450735





0 Likes
gleach1 Absent Member.
Absent Member.

Re: NCC and curl: (60) SSL certificate problem, verify that

I ran into this a few days ago while trying to upgrade several servers, didn't come across this thread though since it's only new... royal pain in the arse

I did the following after finding a tip from someone

mv /usr/bin/curl /usr/bin/curl.bin
vi /usr/bin/curl
(insert these lines)
#!/bin/bash
curl.bin -k $*

save and close it
chmod 755 /usr/bin/curl

run your NCC / suse_register and everything is now happy, of course after each patch / upgrade you need to do the same editing thing again as the upgrade replaces the curl file

you would think that the current patch level would include the certs package with it, I was updating the servers to the latest patch level and it didn't come down...

0 Likes
Knowledge Partner
Knowledge Partner

Re: NCC and curl: (60) SSL certificate problem, verify that the

On 18/01/2012 14:38, T. Bowman wrote:

> Aha! With Googling, I was able to find it on Novell's site. Does anyone
> else still miss the old support site before it was revamped 4 or 5 years
> ago?
>
> Anyway, here's the TID:
> http://www.novell.com/support/dynamickc.do?cmd=show&forward=nonthreadedKC&do
> cType=kc&externalId=7008662&sliceId=1


TID 7010008 is the correct one to use and also links to the following
download but in addition links to an updated suseRegister RPM.

> and a link to the download page (which is also in the TID:
> http://download.novell.com/protected/Summary.jsp?buildid=_7Pup8oi5zw~
>
> And some search terms Google will catch:


TID 7009935 perhaps? That was a TID I'd previously refer you to but has
now been rewritten to address SMT.

> This resolved my issues with curl error 60 and download patches from Novell.
> I don't have an SMT server. Installing the openssl-certs package resolved
> the issue.


HTH.
--
Simon
Novell/SUSE/NetIQ Knowledge Partner

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.