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.
+++ This bug was initially created as a clone of Bug #1661338 +++
krb5 pkinit_anchors should default to FILE:/etc/pki/tls/certs/ca-bundle.crt
When setting up a system for pkinit, it seems odd that the trusted anchors doesn't default to the system provided trust anchors. This can lead to extra configuration work on the users to set a system expected value.
krb5 should default kinit_anchors to the official ca-bundle packaged with the distribution.
Please do not do this.
Unless krb5 was updated between 1.15.1-37.el7_7.2 and 1.16.1-22.el8, the behavior of pkinit.so is to include *every* CA certificate discovered by the pkinit_anchors setting in the AS-REQ request.
ca-bundle.crt currently has around 138 certificates. For a large site, setting pkinit_anchors to FILE:/etc/pki/tls/certs/ca-bundle.crt is effectively a DoS amplification attack against the KDC.
As long as pkinit.so sends every CA certificate it can find in the AS-REQ request, pkinit_anchors should only be set by the local administrator, to contain only the CA certificates that need to be present for the particular smartcard in use. It should not be set globally.
Additionally, note that when the parser encounters the syntactically incorrect "pkinit_anchors = /etc/pki/tls/certs/ca-bundle.crt" setting, it silently aborts the PKINIT attempt, which is fiendishly difficult to debug.
For more details, see BZ#1757506.
You've provided the same comment on multiple bugs, but I'm going to keep replies here. Please note that *this is the bug for the issue you filed* - it doesn't help to point out that it's an issue. I already know that :)
If pkinit is to be used, one of two things must be true: either the certificates are anchored into the default trust, or they aren't. If they are, then this speeds up configuration. But if they're not, the admin would have had to perform additional configuration anyway - the defaults didn't work for them before, and they don't work now.
Do you actually observe slowdown in a case where the default configuration would work for you? cacert processing should be very fast on modern machines.
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:3516