Disabling new D-Bus protocol features by default

Lennart Poettering mzqohf at 0pointer.de
Tue Nov 9 14:29:50 PST 2010

On Tue, 09.11.10 08:33, Thiago Macieira (thiago at kde.org) wrote:

> On Tuesday, 9 de November de 2010 02:07:16 Lennart Poettering wrote:
> > Supporting this per-connection will not work. If at all you need to make
> > this a per-filter flag. But I personally I believe that applications
> > which cannot deal with the data they receive should be fixed. It is
> > always a problem if apps choke if somebody sends them a different data
> > type then they expect. And whether that unexpected data type a classic
> > type, or a new one, doesn't really matter here. 
> You know, the code that is broken here is our own: libdbus-1. It disconnects 
> when a new type is received. So a D-Bus 1.4 client cannot talk to a D-Bus 1.2 
> client. That's why you added the negotiation feature in the first place, 
> remember?

Hmm? Are you suggesting that libdbus 1.2 client somehow negotiate unix
fd support but then choke on that? How would that be possible?

> > Can you point us to actual problem reports for this?
> Right now, only theoretical. I might be splitting hairs here, but I'm trying 
> to fix this before it becomes a real problem.
> Crashing ConsoleKit, PolicyKit, Hal, Avahi or other system services from a 
> non-privileged connection sounds serious to me.

Then let's talk if we have a real-life encounter with this problem!


Lennart Poettering - Red Hat, Inc.

More information about the dbus mailing list