This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2209445 - /etc/krb5.conf.d/kcm_default_ccache is included in the install image when the KCM is not. [NEEDINFO]
Summary: /etc/krb5.conf.d/kcm_default_ccache is included in the install image when the...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lorax
Version: 8.7
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-23 22:55 UTC by Chance Callahan
Modified: 2023-09-18 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 13:50:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:
bcl: needinfo? (ccallaha)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4657 0 None Migrated None 2023-09-18 13:50:38 UTC
Red Hat Issue Tracker RHELPLAN-157979 0 None None None 2023-05-23 22:55:52 UTC

Description Chance Callahan 2023-05-23 22:55:22 UTC 
If a customer is using a custom krb5.conf file, it may include the following line:

includedir /etc/krb5.conf.d/

That directory has an include file that enables the Kerberos Credential Manager, which isn't part of the install live image. When an install image is built, that folder should be cleared of its contents to avoid issues.
Comment 1 Ding-Yi Chen 2023-05-23 23:52:45 UTC 
A thumb of gold is always: do not install the function you don't need.

Thus remove sssd-kcm or don't install it at all will be better.


The consequence of removing the includedir /etc/krb5.conf.d is:

1. Some customers explicit use /etc/krb5.conf.d to organize their realm setting. They will complain about why those settings do not work 
2. Kerberos crypto-policies won't apply, thus potential security risk.
Comment 2 Chance Callahan 2023-05-23 23:54:41 UTC 
Yeah, that's a better idea now that you mention it.
Comment 3 Jiri Konecny 2023-05-25 09:31:19 UTC 
This needs to be done during the ISO build. Switching to Lorax component which is responsible for this.
Comment 4 Brian Lane 2023-05-25 17:00:07 UTC 
It's not clear to me what the problem is. On the boot.iso created by lorax /etc/krb5.conf file and the contents of /etc/krb5.conf.d/ are the defaults. Looking at a RHEL 8.8 iso the crypto-policies file has:

[libdefaults]
permitted_enctypes = aes256-cts-hmac-sha1-96 aes256-cts-hmac-sha384-192 camellia256-cts-cmac aes128-cts-hmac-sha256-128 aes128-cts-hmac-sha1-96 camellia128-cts-cmac

in it. That doesn't look to me like it is enabling 'Kerberos Credential Manager' and I do not see `/etc/krb5.conf.d/kcm_default_ccache` on the iso.

I'm actually not sure how someone would even use kerberos during installation, kickstart doesn't have any commands to set it up, nor does dracut as far as I can tell.

So I have to ask some questions:
What install image are you talking about?
Where did you get it from?
Can you point me to it so I can examine it?
Are you sure it is a boot.iso created by Lorax?

Thanks,

Brian
Comment 5 RHEL Program Management 2023-09-18 13:48:17 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 6 RHEL Program Management 2023-09-18 13:50:47 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.
Note You need to log in before you can comment on or make changes to this bug.