Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
CA certificates are now imported with correct trust flags
Previously, the "pki client-cert-import" command imported CA certificates with `CT,c,` trust flags, which was insufficient and inconsistent with other PKI tools. With this update, the command has been fixed and now sets the trust flags for CA certificates to `CT,C,C`.
Description of problem:
client-cert-import --ca-cert should import CA cert with trust bits "CT,C,C"
Version-Release number of selected component (if applicable):
pki-ca-10.4.1-7.el7.noarch
How reproducible:
always
Steps to Reproduce:
[root@vm-idm-011 slapd-pki]# pki -d . -C password.txt client-cert-import "CA Certificate" --ca-cert ca.crt
-------------------------------------
Imported certificate "CA Certificate"
-------------------------------------
[root@vm-idm-011 slapd-pki]# certutil -L -d .
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI
CA Certificate CT,c,
Actual results:
Expected results:
The trust bits should be set to "CT,C,C"
Additional info:
Comment 2Endi Sukma Dewata
2017-06-03 02:06:50 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-2017:2110
Description of problem: client-cert-import --ca-cert should import CA cert with trust bits "CT,C,C" Version-Release number of selected component (if applicable): pki-ca-10.4.1-7.el7.noarch How reproducible: always Steps to Reproduce: [root@vm-idm-011 slapd-pki]# pki -d . -C password.txt client-cert-import "CA Certificate" --ca-cert ca.crt ------------------------------------- Imported certificate "CA Certificate" ------------------------------------- [root@vm-idm-011 slapd-pki]# certutil -L -d . Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI CA Certificate CT,c, Actual results: Expected results: The trust bits should be set to "CT,C,C" Additional info: