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.
Bug 2120686 - Keylime configuration is too complex
Summary: Keylime configuration is too complex
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: keylime
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anderson Sasaki
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 2123360
TreeView+ depends on / blocked
 
Reported: 2022-08-23 14:22 UTC by Anderson Sasaki
Modified: 2022-11-15 11:40 UTC (History)
7 users (show)

Fixed In Version: keylime-6.5.0-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2123360 (view as bug list)
Environment:
Last Closed: 2022-11-15 10:34:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-131997 0 None None None 2022-08-23 14:34:44 UTC
Red Hat Issue Tracker SECENGSP-4727 0 None None None 2022-08-23 14:34:46 UTC
Red Hat Product Errata RHBA-2022:8189 0 None None None 2022-11-15 10:34:30 UTC

Description Anderson Sasaki 2022-08-23 14:22:05 UTC 
Description of problem:
Keylime configuration file is confusing and does not have an intuitive option naming. The TLS configuration for the components is confusing, making difficult to the user to create the intended configuration. Moreover, Keylime uses a single configuration file for all components, making it even more confusing when the user wants to deploy each component in a different machine.

Keylime should use individual configuration files for each component, with intuitive option naming, and easy TLS configuration. A proposal for such changes is approved upstream and available in [1].

If the changes are not introduced with Keylime since the beginning (from RHEL-9.1), both the old and new configuration file formats will have to be supported during the whole RHEL-9 lifetime.

[1] https://github.com/keylime/enhancements/blob/master/72_config_and_simplify_tls.md

Version-Release number of selected component (if applicable):
keylime-6.4.2-2.el9

How reproducible:
deterministic

Steps to Reproduce:
1. Open the configuration file installed at /etc/keylime.conf

Actual results:
The configuration for all components are in the /etc/keylime.conf file.
The TLS configuration for each component is confusing.
The options names are not intuitive.

Expected results:
The configuration for each component is in an individual file.
The TLS configuration is clear and simple.
The options names are intuitive, and their purposes are documented.

Additional info:
Comment 17 errata-xmlrpc 2022-11-15 10:34:25 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 (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-2022:8189
Note You need to log in before you can comment on or make changes to this bug.