[Bug 46882] New: Make per-connection bus names non-mandatory

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Mar 2 11:18:39 CET 2012


https://bugs.freedesktop.org/show_bug.cgi?id=46882

             Bug #: 46882
           Summary: Make per-connection bus names non-mandatory
    Classification: Unclassified
           Product: Telepathy
           Version: git master
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: mikhail.zabaluev at nokia.com
         QAContact: telepathy-bugs at lists.freedesktop.org


In the current spec, each Connection object must get its own, dynamically
composed, bus name.
This does not work well on a bus where arbitrary name ownership is prohibited
by policy: while we can easily punch holes for connection manager names, the
connection names are not known statically, and partial name matching is not
currently supported by dbus-daemon policies. Citing dbus-daemon(1):

       Complex  globs  like  "foo.bar.*" aren't
       allowed for now because they'd be work to implement and maybe encourage
       sloppy security anyway.

Taking into account that all components that have been instantiating Connection
objects to date also own ConnectionManager service names, the preferred way to
enumerate Connection objects on the bus could be changed to listing
ConnectionManager services and then enumerating Connection objects on these
services. The requirement for a Connection to register its own bus name can be
relaxed to "SHOULD (for backwards compatibility)". The implementation of
TpBaseConnection in telepathy-glib can then be changed to treat the failed name
ownership request as non-fatal (and get rid of one more complete bus roundtrip
needed to initalize a connection).

I don't see how this change can impact session bus setups where name ownership
is promiscuous (at least for the session user's connections). There are no
backwards compatibility concerns for ownership-restricted bus configurations,
because connection managers cannot currently work there.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.



More information about the telepathy-bugs mailing list