Bug 1905927 - [RFE] update keytab entries when renewing the machine account password
Summary: [RFE] update keytab entries when renewing the machine account password
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: samba
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Pavel Filipensky
QA Contact: Denis Karpelevich
URL:
Whiteboard: review
Depends On:
Blocks: 2211854
TreeView+ depends on / blocked
 
Reported: 2020-12-09 10:52 UTC by Sumit Bose
Modified: 2023-07-04 12:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-01 07:27:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Samba Project 6750 0 None None None 2020-12-09 10:52:10 UTC

Description Sumit Bose 2020-12-09 10:52:10 UTC
Description of problem:
Current, when automatically updating the machine account password winbind only add the new password to the secrets.tdb but does not update the Kerberos keys in the keytab which are derived from the machine account password. As a result, after the update the keytab entries can neither be used for authentication nor to uncrypt and verify server tickets.

If 'kerberos method = secrets and keytab' (and maybe for 'system keytab' or 'dedicated keytab' as well?) winbind should create new entries in the keytab with updated KVNO and new hashes derived from the new machine account password.

Upstream ticket: https://bugzilla.samba.org/show_bug.cgi?id=6750

Comment 1 Andreas Schneider 2020-12-09 12:37:50 UTC
We could get the service principal names from the keytab and then create new entries for each of them, however there is an issue with the kvno to get it right.

Comment 4 RHEL Program Management 2022-08-01 07:27:52 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 6 Pavel Filipensky 2022-08-02 08:43:09 UTC
Hi Andre,

thanks for spotting this. yes, this is a strech goal for Q3. I will reopen it.

Pavel


Note You need to log in before you can comment on or make changes to this bug.