Bug 675165

Summary: bugzilla.redhat.com not trusted by /etc/pki/tls/certs/ca-bundle.crt
Product: [Fedora] Fedora Reporter: Kamil Dudka <kdudka>
Component: ca-certificatesAssignee: Joe Orton <jorton>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: high    
Version: 14CC: jorton, npajkovs, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-04 15:11:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 669984    

Description Kamil Dudka 2011-02-04 14:18:39 UTC
Version-Release number of selected component (if applicable):
ca-certificates-2010.63-3.fc14.noarch

Steps to Reproduce:
echo | openssl s_client -CAfile /etc/pki/tls/cert.pem -connect bugzilla.redhat.com:443 2>&1 | grep Verify

Actual results:
    Verify return code: 21 (unable to verify the first certificate)

Expected results:
    Verify return code: 0 (ok)

Additional info:
The problem may be also on the server's side.

Comment 1 Joe Orton 2011-02-04 14:59:29 UTC
Works fine here.  Please attach the complete output from the command.

depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority
verify return:1
depth=2 C = US, O = GeoTrust Inc., CN = GeoTrust Global CA
verify return:1
depth=1 C = US, O = "GeoTrust, Inc.", CN = GeoTrust SSL CA
verify return:1
depth=0 serialNumber = bcTlha1YkNcz9-M0vAzRilv01xaCkiRQ, C = US, ST = North Carolina, L = Raleigh, O = Red Hat Inc, OU = Information Technology, CN = bugzilla.redhat.com
verify return:1

Comment 2 Kamil Dudka 2011-02-04 15:11:17 UTC
It started to work for me as well a while ago.  It looks like a temporary issue, but not related to my configuration since other people were observing the same problem, too -- bug 669984

I am closing the bug now.  Hopefully the problem has been solved somewhere else.