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.

Description of problem:

The option require_ek_cert tells the tenant whether to require an EK certificate from the TPM, and is recommended to be used in production deployments.

When keylime is doing the initial identity quote and require_ek_cert is enabled, it will attempt to verify that the TPM device on the agent is genuine, based on its EK certificate, which will be validated against the trusted certificates present in the keylime TPM certificate store.

However, a few of the certificates -- namely a few issued by Nuvoton -- in the TPM certificate store are malformed x509 certificates, which will then cause an issue as they are attempted to be parsed. 

It's possible that during the EK validation, one of those certificates are read, which then causes the issue described here.

Version-Release number of selected component (if applicable):
keylime <= 6.5.1


Additional info:
This issue was fixed upstream here: https://github.com/keylime/keylime/pull/1156

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 (keylime bug fix and enhancement update), 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-2023:2307