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 dbus specfile creates a `dbus` user and group with `81` as static IDs:
https://src.osci.redhat.com/rpms/dbus/blob/rhel-8.6.0/f/dbus.spec#_295
However the `dbus-common` package ships a sysusers.d fragment under `/usr/lib/sysusers.d/dbus` which creates a user/group with dynamic ID allocation:
```
# sysusers.d snippet for creating the D-Bus system user automatically
# at boot on systemd-based systems that ship with an unpopulated
# /etc. See sysusers.d(5) for details.
u dbus - "System Message Bus"
```
To fix misalignment, it would be good to update the sysusers fragment to use `81` as the UID/GID too.
This also affects Fedora and RHEL9. I didn't want to create a swarm of duplicate tickets, but it would be good to start fixing it there until eventually reaching 8.6.
Hmm. I think though in theory, dbus could actually use a dynamic user. Or really even better, there's no reason AFAIK it couldn't use `DynamicUser=yes` and not use sysusers or useradd at all.
It turned out that there are filesystem entries in OS content owned by the `dbus` user/group, so a dynamic ID is likely not a great solution in this case.
In particular, there is at least a setGID binary shipped by the `dbus-daemon` at `/usr/libexec/dbus-1/dbus-daemon-launch-helper` and owned by the `dbus` group:
https://src.fedoraproject.org/rpms/dbus/blob/f35/f/dbus.spec#_403
For this specific user/group, I believe that a sysusers.d fragment with the Fedora-allocated static UID/GID may be the best option.
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 (dbus 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:7769