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.

Description of problem:

Customer is insisting to include "thawte" CA certificate along with other CA which comes with ca-certificates.

https://search.thawte.com/library/VERISIGN/ALL_OTHER/KB_IMAGES/SO26817/Certs/SHA2/thawte_SHA256_SSL_CA.cer

Latest ca-certificates for RHEL 6.X is ca-certificates-2017.2.14-65.0.1.el6_9.noarch which doesn't contains "thawte" CA.

Following resolved the issue

# update-ca-trust enable

# cp thawte_sha256_ssl.crt  /etc/pki/ca-trust/source/anchors/ 

# update-ca-trust extract

but the customer don't want to perform the same, insisting to include mentioned CA.

Hello.

The provided link doesn't work. I need to see the exact certificate the customer is inquiring about.

Hi,

the search on thawte.com doesn't work anymore. Moved to digicert.com.

You can find the certificate(s) here:
thawte SHA256 SSL CA
https://knowledge.digicert.com/solution/SO26817.html

I assume you're enquiring about this one:
https://knowledge.digicert.com/content/dam/digicertknowledgebase/library/VERISIGN/ALL_OTHER/KB_IMAGES/SO26817/Certs/SHA2/thawte_SHA256_SSL_CA.cer

        Issuer: "CN=thawte Primary Root CA - G3,OU="(c) 2008 thawte, Inc. - For authorized use only",OU=Certification Services Division,O="thawte, Inc.",C=US"

        Subject: "CN=thawte SHA256 SSL CA,O="thawte, Inc.",C=US"

This isn't a root CA. It's an intermediate CA.

We intentionally don't include any intermediate CAs in the ca-certificates package.

A common situation is that clients connect to a server, and the client is unable to verify the server's certificate, because the server didn't include the intermediate.

However, servers are REQUIRED to include the intermediate CAs related to the server's cert in their SSL/TLS handshake message.

In order to do so, the server software must be configured with a copy of the intermediate CA(s).

The CA that issued that server certificate should provide documentation for that.

The server software product that is used should have documentation for configuring intermediate CAs.