upstart-dbus-bridge --system is not started on boot

[Zygmunt Krynicki]

Upstart has a dbus bridge that can convert dbus signals to upstart events. This feature is, however, enabled for only user jobs, not for systems jobs. User jobs can see both session and system level DBus signals *but* system jobs cannot see either.

This is related to https://code.launchpad.net/~jamesodhunt/upstart/upstart-dbus-bridge/+merge/161772/comments/382554

[Zygmunt Krynicki (zyga)]

This is a modified copy of the session-level dbus bridge job that I've just confirmed to work as a system-level job.

[James Hunt (jamesodhunt)]

As the description shows, the reason we do not run the upstart-dbus-bridge at the system level is due to security concerns.

Unless the Security Team feel otherwise, it is probably best to simply document that this bridge does not run by default and if an admin wishes to enable it, they can - we could potentially ship /etc/init/upstart-dbus-bridge.conf along with an override file /etc/init/upstart-dbus-bridge.override containing "manual" such that it is disabled by default but could be enabled by removing the .override file.

Added the Security Team for their input.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.