Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Descriptionjeff.chapin@uni.edu
2019-10-03 13:45:56 UTC
Description of problem:
katallo-rhsm-consumer adds katello.pem to trusted system certificates -- even if it includes certificates already in the system bundles:
Version-Release number of selected component (if applicable):
6.4.3
How reproducible:
100%
Steps to Reproduce:
1. Reinstall katello-ca-consumer
Running Transaction
Updating : katello-ca-consumer-satellite.admin.uni.edu-1.0-5.noarch
p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt
p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt
p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt
p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt
p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt
Cleanup : katello-ca-consumer-satellite.example.com-1.0-2.noarch
Verifying : katello-ca-consumer-satellite.example.com-1.0-5.noarch
Verifying : katello-ca-consumer-satellite.example.com-1.0-2.noarch
2.katallo-rhsm-consumer also directly run creates these errors
3.
Actual results:
p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt
Expected results:
No errors
Additional info:
This causes issues with some FTPs clients -- the error p11-kit: duplicate 'DigiCert High Assurance EV Root CA' certificate found in: ca-bundle.legacy.crt is thrown when they connect
The issue is that Digicert is already in a bundle, before katello tried to add it again.
As far as I know, given we run update-ca-trust to add our CA certificate to the system CA bundle, there isn't a way to avoid this since update-ca-trust looks at the anchors directory and ensures anything added there is in the bundle.
Comment 4jeff.chapin@uni.edu
2019-10-28 12:21:28 UTC
So this is a bug with update-ca-trust? It's causing errors and problems when it adds duplicate certs, or is it a bug with Satellite putting a duplicate cert into the anchors directory?
From my own testing, this appears to be a bug specific to the version in RHEL 6 that provides update-ca-trust. If there is a duplicate certificate present it throws an issue and there isn't an easy way for us to detect that. I'd suggest this be closed won't fix and/or file a RHEL bug to get an update back ported to RHEL 6.