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: tdb files in /var/lib/samba are world-readable [-rw-r--r--.]


Version-Release number of selected component (if applicable):


How reproducible:Always.


Steps to Reproduce:
1. Install IPA server on RHEL7.2
2. Navigate to /var/lib/samba directory


Actual results: Some of the .tdb files are world-readable, which shouldn't be if it isn't really required.

-rw-r--r--. 1 root root    40200 Sep 23 19:22 brlock.tdb
-rw-r--r--. 1 root root    20480 Sep 23 19:28 gencache_notrans.tdb
-rw-r--r--. 1 root root   430080 Sep 23 19:26 gencache.tdb
-rw-r--r--. 1 root root      696 Sep 23 19:22 leases.tdb
-rw-r--r--. 1 root root    40200 Sep 23 19:22 locking.tdb
-rw-r--r--. 1 root root      696 Sep 23 19:22 notify_index.tdb
-rw-r--r--. 1 root root      696 Sep 23 19:22 notify.tdb
-rw-r--r--. 1 root root     8192 Sep 23 19:28 serverid.tdb


Expected results: .tdb file permissions should be consistent with other files in the directory i.e 640 and should be 644 only if required.

Additional info:

Alexander, please help us assess this one.

These files have to be world readable or smbd processes running under specific users wouldn't be able to coordinate locking, for example. This bug is nonsense.