Description of problem:
Customer is insisting to include "thawte" CA certificate along with other CA which comes with ca-certificates.
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.
The provided link doesn't work. I need to see the exact certificate the customer is inquiring about.
the search on thawte.com doesn't work anymore. Moved to digicert.com.
You can find the certificate(s) here:
thawte SHA256 SSL CA
I assume you're enquiring about this one:
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.