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 fix in bug #1828354 (in 7.9 branch) is incomplete and does not work against Windows DC.
Comment 4Andreas Schneider
2020-07-02 12:26:03 UTC
This is an additional fix needed to complete bug #1828354. A Windows DC implicitly adds a short name for each FQDN added to msDS-AdditionalDnsHostName, but it comes with a strage binary suffix "\0$" which we Samba should ignore.
As we don't ignore this this suffix the additonal dnshostnames are not added as entries to the KRB5 keytab we create. The change is simple enough that instead of just using the provided UTF8 string we use a conversion function from UTF8 to the configured unix charset.
If we don't fix this, we will not be able to create correct keytabs which will create problems for customers which need a valid keytab. The change is covered by upstream test and also will be tested by our QA.
Comment 5Andreas Schneider
2020-07-02 12:28:17 UTC
The code only touches the 'net ads keytab create' command. No other components have been changes. It is easy to test and confirm that the tool is working correctly.
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 (samba 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-2020:4069