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.
Bug 1671247 - CC: Enable AIA OCSP cert checking for entire cert chain [rhel-7.6.z]
Summary: CC: Enable AIA OCSP cert checking for entire cert chain [rhel-7.6.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jss
Version: 7.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jack Magne
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On: 1666872
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-31 08:12 UTC by RAD team bot copy to z-stream
Modified: 2019-03-13 18:45 UTC (History)
2 users (show)

Fixed In Version: jss-4.4.4-5.el7_6
Doc Type: Bug Fix
Doc Text:
ause: Previously when configuring a CS subsystem to perform ocsp checking based upon the AIA extension of each cert to be evaluated, the feature would only perform the desired ocsp check on the leaf cert and not the rest of the certificate chain. Consequence: This resulted in a possibly incomplete ocsp verification of a certficate and its chain. If a member of the chain had been revoked, the pki subsystem will still think the leaf cert is valid. Fix: The resolution to this particular issue was to enhance the behavior of the ocsp checking in JSS for ONLY the AIA extension URL checking scenario. When AIA extensions are being consulted, the system has been enhanced to check the leaf cert and the cert chain for verification. Result: As a result, a full verification of a cetificate and its chain can be relied upon to have taken place correctly by interested parties.
Clone Of: 1666872
Environment:
Last Closed: 2019-03-13 18:45:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0505 0 None None None 2019-03-13 18:45:40 UTC

Description RAD team bot copy to z-stream 2019-01-31 08:12:17 UTC
This bug has been copied from bug #1666872 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 5 Asha Akkiangady 2019-02-14 01:11:12 UTC
Marking the bug on Assigned state to fix the ocsp check problem reported by CC lab.

Comment 6 Amol K 2019-03-01 16:41:49 UTC
I tested this bugzilla on 10.5.9-13.el7_6

I followed steps (In #comment 4) which are mentioned by Jack

Observations:
1. I could see the subsystems could hit the Internal OCSP.
2. If key archival is done then it should check the certificate against the CA/SubCA
3. As negative test cases, I revoked RootCA cert. And as expected it was not working.

Verifying this BZ.

Comment 8 errata-xmlrpc 2019-03-13 18:45:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0505


Note You need to log in before you can comment on or make changes to this bug.