Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 749
    • Issues 749
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 319
    • Merge requests 319
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpine
  • aportsaports
  • Issues
  • #3313

Closed
Open
Created Aug 27, 2014 by Rich Felker@dalias

dbus-daemon-launch-helper is installed setuid root as part of dbus package

dbus-daemon-launch-helper is needed only for “D-BUS System Activation”, a feature similar to systemd activation where dbus actually starts daemons itself rather than having them started through the init system with the proper initial privileges, which obviously require a setuid helper. This is described in:

http://dbus.freedesktop.org/doc/system-activation.txt

Such a setup is almost certainly an undesirable risk in a hardened environment, and it’s not clear that it’s needed or useful at all with proper use of OpenRC. Thus, dbus-daemon-launch-helper should not be installed setuid by default. Moving it to a separate package (e.g. dbus-system-activation) may be an appropriate solution.

(from redmine: issue id 3313, created on 2014-08-27)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking