dbus_bus_request_name with bluez

[Andreas Volz]

Am Fri, 30 Oct 2009 19:33:48 -0400 (EDT) schrieb John Palmieri:

> > BTW: I just found out if I start my application as root it also
> > works with enabled exception handling. Have I found a security hole
> > (at least
> > in dbus-python and dbus-send)?
> > 
> > bluez-4.12-0ubuntu5
> 
> Wait, I don't understand.  Are you developing dbus-c++ or are you
> just using dbus-c++?  Why is request_name being called? Requesting a
> name on a connection means you want to register that connection under
> the given common name.  Since bluez already has that name then you
> generate a D-Bus error.  None of the code above, either dbus-send or
> the python code ever calls request_name on the bluez common name so
> you wouldn't get that error. dbus-c++ for some reason is calling
> request_name when it shouldn't or you are using the C++ code wrong.
> Perhaps there is two different connections - one if you want to
> provide a service and another for clients wishing to connect to a
> service?  I've never used them so I am not completely sure.

I develop dbus-c++, but as I didn't start the project I don't know all
technical details. Here I copied a wrong example and wondered why it
doesn't work. As you see in my other post the problem is solved. :-)

regards
	Andreas