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.
The PKINIT implementation for MIT krb5 follows a strict hierarchy for PKCS#11 certificate selection:
module_name -> slotid/token -> certid/certlabel
In case the token is not explicitly configured, krb5 will pick the first one provided by the module[1]. The documentation[2] confirms "certlabel" is meant to be used only once the "device" (i.e. the token) has been selected.
As a result, a certlabel matching one of the certificate on a token which is not the first one in the module, and where the desired token is not explicitly set in the configuration, would cause this certificate to be ignored. This is inconvenient in case a used has multiple smartcards connected in at same time.
The fact we recently switched from OpenSC to p11-kit[3] as default PKCS#11 module in bug 2030981, has the consequence of merging all the tokens from all the available modules into a single one. Which increases slightly the chances such an issue would occur in a scenario involving multiple modules.
A solution would be to lookup the certlabel across all the tokens, in case the latter is not explicitly configured. With such an approach, we should find a way to balance the relevance of the certificate's choice and convenience for the user: certificates might not be visible in the token without prompting its PIN code, which would imply asking for this code for all tokens at each PKINIT pre-authentication.
[1] https://github.com/krb5/krb5/blob/krb5-1.20-final/src/plugins/preauth/pkinit/pkinit_crypto_openssl.c#L3642
[2] https://web.mit.edu/kerberos/krb5-1.20/doc/admin/conf_files/krb5_conf.html#specifying-pkinit-identity-information
[3] https://p11-glue.github.io/p11-glue/p11-kit.html
Comment 4RHEL Program Management
2023-09-18 19:52:25 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-18 19:57:29 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.