Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause: incorrect documentation about loading CA certificates by nickname when using curl program with NSS
Consequence: incorrect documentation
Fix: update the documentation about loading CA certificates with NSS
Result: correct documentation
+++ This bug was initially created as a clone of Bug #696783 +++
Trying to use curl with NSS to do client authentication against a cert-controlled webpage.
[ckannan@localhost test]$ echo $SSL_DIR
/home/ckannan/curl/test
[ckannan@localhost test]$ ls *.db
cert8.db key3.db secmod.db
[ckannan@localhost test]$
[ckannan@localhost test]$
[ckannan@localhost test]$
[ckannan@localhost test]$ certutil -L -d .
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI
testnick P,,
OCSP Administrator of Instance pki-ocsp's pkisilentdomain ID u,u,u
TKS Administrator of Instance pki-tks's pkisilentdomain ID u,u,u
mach1.idm.lab.bos.redhat.com ,,
VeriSign Class 3 Extended Validation SSL CA ,,
wiki.idm.lab.bos.redhat.com ,,
GeoTrust SSL CA ,,
mach1.idm.lab.bos.redhat.com #2 ,,
Certificate Authority - pkisilentdomain CT,C,C
CA Administrator of Instance pki-ca's pkisilentdomain ID u,u,u
KRA Administrator of Instance pki-kra's pkisilentdomain ID u,u,u
RA Administrator's pkisilentdomain ID u,u,u
TPS Administrator's pkisilentdomain ID u,u,u
[ckannan@localhost test]$
[ckannan@localhost test]$
[ckannan@localhost test]$
[ckannan@localhost test]$ curl -v --cert "CA Administrator of Instance pki-ca's pkisilentdomain ID" --cacert "Certificate Authority - pkisilentdomain" --data-urlencode "xmlOutput=true" --data-urlencode "reqCompleted=true" --data-urlencode "reqType=enrollment" --data-urlencode "maxCount=20" "https://mach1.idm.lab.bos.redhat.com:9443/ca/agent/ca/queryReq"
* About to connect() to mach1.idm.lab.bos.redhat.com port 9443 (#0)
* Trying 10.16.96.53... connected
* Connected to mach1.idm.lab.bos.redhat.com (10.16.96.53) port 9443 (#0)
* Initializing NSS with certpath: /home/ckannan/curl/test
* NSS error -5978
* Closing connection #0
* Problem with the SSL CA cert (path? access rights?)
curl: (77) Problem with the SSL CA cert (path? access rights?)
[ckannan@localhost test]$
--- Additional comment from Kamil Dudka on 2011-04-14 22:41:27 CEST ---
You cannot specify a CA certificate by nickname.
--- Additional comment from Kamil Dudka on 2013-01-28 14:36:46 CET ---
upstream commit:
https://github.com/bagder/curl/commit/11dde6ac
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1695.html