[Bluez-devel] Improving the PIN request a little bit

[Marcel Holtmann <marcel@holtmann.org>]

Hi,

I like to improve the PIN request stuff and my plan is to follow the
SuSE approach. Right now the hcid can use /etc/bluetooth/pin for
incoming connection or call the PIN helper. I like to move everything
into the PIN helper program and let this decide wether to return with a
fixed PIN from a file or call a GUI tool. This also means that I plan to
deprecated the Python based script and so remove the dependancy on
Python and Python-GTK. I like to have a simple shell script that may
call the bluez-pin binary or the KDE tool for it or whatever depending
on what is installed/configured and what desktop is running. If it fails
it falls back to the /etc/bluetooth/pin file and sends that string back
to the hcid. Comments?

Maybe it is also a good idea to do the same for the link key. Any ideas?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel