Re: [Bluez-devel] D-Bus support

[Marcel Holtmann <marcel@holtmann.org>]

Hi Fredrik,

> > My problem is now that I don't wanna link the Bluetooth library itself 
> > with the D-Bus library. So what I was thinking of that we extend the 
> > hcid to be a multiplexer with a D-Bus interface. So we have the HCI raw 
> > socket and ioctl's for configuration and we can use the D-Bus interface 
> > for this and also advanced things like PIN management etc. My idea behind
> > this is, that graphical interfaces like Gnome or KDE only have to use the 
> > D-Bus for their stuff.
> 
> I have implemented this in hcid, DBus sockets, Gnome configuration
> interface and so on. Please look at: http://noring.nocrew.org/bluetooth/

I already looked at your stuff. Nice work btw. At the moment I am more
concerned on how the D-Bus interface should look like than a real
implementation. You now that an important part for me is the security.
For example a user can see what devices a paired and it can delete a
pairing, but it don't have to see the link key itself. This is the job
of the daemon that provides this interface. The same applies for
changing device settings and storing them on the harddisk.

Another point is that I want to use the system message bus for it.

> > Proposals and comments?
> 
> Later tonight, I'll write you a detailed description on what's already
> implemented on the hcid DBus interfaces, new configuration options, the
> nametab and keytab files etc. I'd like to discuss these things so that
> we can agree on the API:s etc.

My favourite storage is Berkeley DB.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel