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.
Bug 2259026 - Add feature in katello-certs-check to verify if CA bundle has any certificates with trust rules
Summary: Add feature in katello-certs-check to verify if CA bundle has any certificate...
Keywords:
Status: POST
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.14.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-18 17:39 UTC by Joniel Pasqualetto
Modified: 2024-05-16 16:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37063 0 Normal Closed Add feature in katello-certs-check to verify if CA bundle has any certificates with trust rules 2024-04-03 18:25:30 UTC
Red Hat Issue Tracker SAT-22567 0 None None None 2024-01-18 17:41:31 UTC
Red Hat Knowledge Base (Solution) 7052878 0 None None None 2024-01-22 20:40:48 UTC

Description Joniel Pasqualetto 2024-01-18 17:39:33 UTC 
Description of problem:

Trust rules on a certificate indicate what are the accepted uses for it. Some users may have a CA bundle where one of the certificates includes trust rules (maybe incorrectly). 

The default validation done by katello-certs-check does not complain about it. The bundle can be used without problems on Satellite 6.14+ but fails on 6.13 (at least, didn't check older versions).

Also, when thinking about clients of Satellite, RHEL8+ can trust the bundle that contains trust rules but RHEL7 will have problems (when using libcurl) trusting that.

So, accepting a bundle like this will potentially break the Satellite installation (foreman-proxy is the component failing on 6.13 when using it) and also break the access to Satellite for RHEL7 hosts.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:

1. Have a CA certificate and add a trust rule to it:

~~~
openssl x509 -in ca_cert.pem -addtrust serverAuth -out ca_trust_rule.pem
~~~

2. Check with katello-certs-check and there will be no complaints about it.

Actual results:

katello-certs-check does not complaint about having a CA bundle in a format that may break satellite and/or client access to satellite

Expected results:

katello-certs-check should point that there is an issue with the bundle

Additional info:
Comment 4 Eric Helms 2024-05-16 16:18:10 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37063 has been resolved.
Note You need to log in before you can comment on or make changes to this bug.