[Bug 1234653] Re: upstart-dbus-bridge --system is not started on boot

[James Hunt]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1234653

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

Status in “upstart” package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1234653/+subscriptions