Bug 1666872
| Summary: | CC: Enable AIA OCSP cert checking for entire cert chain | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jack Magne <jmagne> | |
| Component: | jss | Assignee: | Jack Magne <jmagne> | |
| Status: | CLOSED ERRATA | QA Contact: | Asha Akkiangady <aakkiang> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.7 | CC: | ascheel, cpelland, mharmsen, msauton, prisingh | |
| Target Milestone: | rc | Keywords: | TestCaseProvided, ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | jss-4.4.6-1.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1666907 1671247 (view as bug list) | Environment: | ||
| Last Closed: | 2019-08-06 13:06:56 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1666907, 1671247 | |||
|
Description
Jack Magne
2019-01-16 20:01:04 UTC
Commit in JSS: v4.4.x: f609ff042970a30015862f3a962f52c631780dd0 Resolve Bug 1666872 - CC: Enable AIA OCSP cert checking for entire cert chain. This fix for jss, solves the one use case where the pki server is configured to perform ocsp checking ONLY with the contents of the AIA extension. Previously, jss could only check the ocsp server for the leaf node cert of the cert being verified. This fix allows the cert chain to be checked over ocsp for each cert in question. This is possible due to the fact that we have made a call in the PKIX library of nss to do the actual cert verfication. This call is made with all the needed flags to tell the PKIX library to make the ocsp verifications remotely over the network using the contents of the AIA extension. Later on we can use this code to handle the other cases, but for now we want to solve this one particular problem. If the server is configured in any other configuration than the one stated, the original verification code will be called as before. Below is an example of a configuration in server.xml, that will trigger this new code: < .... enableOCSP="true" ocspCacheSize="10000" ocspMinCacheEntryDuration="7200" .... > Note that due to ocsp caching, the cert chain verification may only be apparent after a restart of the server. A way to force an ocsp fetch every time is to set the value of ocspCacheSize=-1, which essentially disables the cache. Added a couple of minor fixes due to review comments. Possibly more to come. Minor include directive change to compile on branch. Author: jmagne RHEL Version: [root@pki1 test_dir]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.7 Beta (Maipo) PKI Version: [root@pki1 test_dir]# pki --version PKI Command-Line Interface 10.5.16-2.el7 JSS Version: [root@pki1 test_dir]# rpm -qa | grep jss jss-4.4.6-1.el7.x86_64 Step of reproduction: https://bugzilla.redhat.com/show_bug.cgi?id=1666872#c7 Proof of concept: Log has been attached. 1. While going through the verification steps i can see one entry in the subCA's debug log and one entry in the Root CA's debug log which represent the chain. 2. In KRA's server.xml updated enableOCSP='false' to enableOCSP='true' and removed ocspResponderURL, ocspResponderCertNickname params. Restarted the KRA. Seeing multiple ocsp hits in the SUBCA's debug log for the various system certs and only one hit in the Root CA's debug log for the SUBCA's signing cert for the chain. Hence, Marking this bugzilla as verified. 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:2219 |