Hi, On Tue, Sep 15, 2009, Florian Philipp wrote: > Just out of curiosity: Why does Bluez no longer provide any kind of > deamon as a pin helper any more? Isn't that exactly what the two command line based agents are if you run them in the background and modify them to always accept pairing requests? Or am I misunderstanding your question? Note that we can't anymore have interfaces which just deal with a simple PIN. Bluetooth 2.1 SSP brings along it's own set of callbacks that need handling and any interface that we define (be it a config file, D-Bus or something else) needs to take that into account. > I mean, it's not like Bluetooth itself is limited to interactive systems > which rightly demand graphical interfaces nowadays. Stuff like NAP is a > classic client-server situation in which you don't want to use Gnome or > KDE apps on the server side and maybe not even on the client side. The current agent interface design doesn't restrict you in any way to interactive systems. It merely exports the pairing callbacks from bluetoothd to an external process. bluetoothd doesn't care if that process does some interactive stuff or not. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
