New version of bluez uses a different way to ask Pin from the user. It is now dbus based instead of configuring the helper in the config file. Please update the guide accordingly. If you need help with what to write just say so and I will try to elaborate more. http://www.gentoo.org/doc/en/bluetooth-guide.xml
(In reply to comment #0) > New version of bluez uses a different way to ask Pin from the user. It is now > dbus based instead of configuring the helper in the config file. Please update > the guide accordingly. If you need help with what to write just say so and I > will try to elaborate more. Correct; we need to know what to change. While a patch using diff -Nut against the raw XML is always nice, a simple text file of what to change or further explanation in a comment will do.
(In reply to comment #1) > > Correct; we need to know what to change. While a patch using diff -Nut against > the raw XML is always nice, a simple text file of what to change or further > explanation in a comment will do. > Dick please take a look a the guide and see if you have some other changes in mind wrt >=3.
I will check out bluetooth-guide.xml and try to create an unified diff. Please give me some hints about writing Gentoo documentation. From http://wiki.bluez.org/wiki/Security "pin_helper concept has been removed starting with bluez-utils 3.X. and has been replaced with a feature called passkey agents. An application that wants to handle passkey requests must use the "hcid" security interface to register a passkey agent. Currently, two types of passkey agents are supported: default and device specific. A "specific" passkey agent handles all passkey requests for a given remote device while a default handles all requests for which a specific agent was not found. "specific" passkey agents are useful to address pre-defined passkey values or environments where the user interaction is not allowed/difficult." The default passkey agent can by installed by emerging net-wireless/bluez-gnome or net-wireless/kdebluetooth (untested). If you don't have a (compatible) graphical desktop you can use /usr/bin/passkey-agent from net-wireless/bluez-utils. Josh, please tell me if you have more suggestions.
(In reply to comment #3) > The default passkey agent can by installed by emerging net-wireless/bluez-gnome > or net-wireless/kdebluetooth (untested). If you don't have a (compatible) > graphical desktop you can use /usr/bin/passkey-agent from > net-wireless/bluez-utils. > > Josh, please tell me if you have more suggestions. > The text you quoted is mostly irrelevant to both the guide and this bug report. Just so ya know. Near as I can tell, basically I should just add directions to install bluez-gnome or kdebluetooth as their pin helper. If users don't want to install either of those, they should emerge bluez-utils and use the passkey-agent utility. Let me know if this is correct. If so, can I get a very small usage example for all three of these applications, or at least for passkey-agent?
(In reply to comment #4) > > Near as I can tell, basically I should just add directions to install > bluez-gnome or kdebluetooth as their pin helper. If users don't want to install > either of those, they should emerge bluez-utils and use the passkey-agent > utility. Let me know if this is correct. If so, can I get a very small usage > example for all three of these applications, or at least for passkey-agent? > bluez-utils must be installed to even get the notifications as it's the daemon in there sending them. Usage: bluez-gnome start bluetooth-applet (Looking at the autostart file, it should start automatically: [Desktop Entry] Encoding=UTF-8 Name=Bluetooth Manager Comment=Bluetooth Manager applet Icon=stock_bluetooth Exec=bluetooth-applet Terminal=false Type=Application Categories= OnlyShowIn=GNOME; kdebluetooth start kbluetoothd (Can be started from the menu) passkey-agent: betelgeuse@pena ~ $ passkey-agent 1234 00:10:DC:E9:13:00 betelgeuse@pena ~ $ passkey-agent --default 1234 Passkey request for device 00:17:4B:19:51:93 The first version listen to a certain device and the second to all as I understand it. You just give it the pin and it always uses that one.
Fixed in CVS. Thanks for reporting, and thanks to Betelgeuse for answering questions on IRC.
