Bug 1502527
| Summary: | CA cert without Subject Key Identifier causes issuance failure [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | pki-core | Assignee: | Fraser Tweedale <ftweedal> |
| Status: | CLOSED ERRATA | QA Contact: | Asha Akkiangady <aakkiang> |
| Severity: | urgent | Docs Contact: | Petr Bokoc <pbokoc> |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | ftweedal, gparente, mharmsen, msauton, nicolai, pbokoc, rhcs-maint, tscherf |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pki-core-10.4.1-16.el7_4 | Doc Type: | Bug Fix |
| Doc Text: |
An earlier update to pki-core mistakenly removed a fallback procedure to Issuer Key Identifier. This caused certificate issuance to fail if the CA signing certificate did not have a Subject Key Identifier extension. In this update, the fallback procedure is restored, and certificate issuance now succeeds in cases where the CA signing certificate does not have the SKI extension.
|
Story Points: | --- |
| Clone Of: | 1499054 | Environment: | |
| Last Closed: | 2017-11-30 15:32:00 UTC | Type: | --- |
| 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: | 1499054 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-10-16 07:42:34 UTC
ftweedal: Fixed upstream: 8ec0cbd1bef372ed50e19f6c5b6332b75209beb0. Verification notes from Amol:
After providing the CA certificate, installation is successful.
I'm able to see the SKI extension in Signing certificate.
```
Name: Certificate Subject Key ID
Data:
54:72:85:a1:2d:3d:3f:f0:80:0b:4a:1b:6b:97:0b:e8:
67:f0:6c:43
```
Verifying this bug.
pki-version : 10.4.1-16.el7_4
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-2017:3301 |