Summary: | hald_dbus.c:4080: dbus_bus_get(): Did not receive a reply | ||
---|---|---|---|
Product: | dbus | Reporter: | bbouillon <b.bouillon> |
Component: | core | Assignee: | Havoc Pennington <hp> |
Status: | RESOLVED NOTOURBUG | QA Contact: | John (J5) Palmieri <johnp> |
Severity: | normal | ||
Priority: | high | Keywords: | security |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
bbouillon
2007-05-23 03:28:27 UTC
after changing /etc/passwd file attribute you can reproduce this bug at any times. to do that just apply the command below $ chmod o-r /etc/passwd now restart the haldaemon and it doesn't work can't restrict /etc/passwd to chmod o-rwx. haldaemon and avahi-daemon fail after doing that The error indicates: IMO this is not a HAL but may a DBus problem. Reassign to DBus. user "messagebus" (or whatever the dbus daemon runs as on your system) has to be able to call libc functions like getpwnam(), which means libc is reading /etc/passwd behind the scenes. If you break your libc by setting weird permissions on /etc/passwd I see no reason to expect that to work. If you want to do this, you would have to either put the bus daemon user in a group that can read /etc/passwd, or you would have to do something more complex with selinux or change how all the bus daemon policies for things like HAL work to not rely on knowing the userid of the hal user, since /etc/passwd isn't readable to get that userid. Or I may totally misunderstand, to diagnose this 100% for sure someone would have to do a dbus message bus verbose log or something. Anyway basically this is in the category of "don't do things that break your system." If you want to make /etc/passwd not readable, then you have to change the system in other ways to be sure things that need to read it still can. That's either a distribution or site local problem. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.