Yes, tried that. I think the config must be changed because it looks like a documented feature.
See man dbus-daemon, the section about policies:
Policies are applied to a connection as follows:
- all context="default" policies are applied
- all group="connection’s user’s group" policies are applied
in undefined order
- all user="connection’s auth user" policies are applied
in undefined order
- all at_console="true" policies are applied
- all at_console="false" policies are applied
- all context="mandatory" policies are applied
Policies applied later will override those applied earlier, when the
policies overlap. Multiple policies with the same user/group/context
are applied in the order they appear in the config file.
Looked to me like the at_console policy denies the sending of the messages, because
it is applied after the user = root policy. In the logs one could clearly see, that there were messages
denied due to some config rules.
Yes, tried that. I think the config must be changed because it looks like a documented feature.
See man dbus-daemon, the section about policies:
Policies are applied to a connection as follows:
- all context="default" policies are applied
- all group="connection’s user’s group" policies are applied
in undefined order
- all user="connection’s auth user" policies are applied
in undefined order
- all at_console="true" policies are applied
- all at_console="false" policies are applied
- all context="mandatory" policies are applied
Policies applied later will override those applied earlier, when the
policies overlap. Multiple policies with the same user/group/context
are applied in the order they appear in the config file.
Looked to me like the at_console policy denies the sending of the messages, because
it is applied after the user = root policy. In the logs one could clearly see, that there were messages
denied due to some config rules.