1. 09 Oct, 2014 1 commit
  2. 07 Oct, 2014 1 commit
  3. 25 Sep, 2014 2 commits
  4. 18 Mar, 2011 1 commit
    • Colin Walters's avatar
      bus: Rewrite a11y bus management, don't fall back to session bus · ce599c14
      Colin Walters authored
      First of all, there should *always* be an a11y bus; if I enable
      toolkit-accessibility, and apps pick that up but then libat-spi falls
      back to the session bus, that's broken.
      
      Fix this by rewriting the a11y bus launcher in C, making it a persistent
      session service, and giving it a DBus API (bus name: org.a11y.Bus).  It
      will start the bus process as a child dynamically; however if
      toolkit-accessibility is enabled, we start it on startup.  For more
      information, see the new file bus/README.
      
      Details:
      
      * Create a .service file so the session bus autostarts us if
        necessary
      * The .desktop file is changed to use --start-immediately
      * Remove the kill_accessibility_bus() hack in registryd; instead
        we chain at-spi-bus-launcher to the session bus lifecycle.
      * Change at-spi bus lookup to try both the new session bus API
        and the X11 root window property.
      * Create libregistry-internals.la which encapsulates a11y bus
        lookup logic, de-duplicating from atspi/ and registryd/.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=644851
      ce599c14
  5. 07 Mar, 2011 1 commit
    • Mike Gorse's avatar
      Fix for BGO#643110: Do not allow all users to connect to the accessibility bus · 7783b5e6
      Mike Gorse authored
      Allowing all users to connect to the accessibility bus creates a security
      issue where one user could control applications being run by another user.
      So we'll only allow root to connect, so that applications running as root are
      still accessible.  This assumes that dbus-daemon is running as the user who
      is currently logged in.
      7783b5e6
  6. 24 Aug, 2010 2 commits
  7. 17 Dec, 2009 1 commit