On Tue, 2004-01-27 at 00:10, Marcel Holtmann wrote:

> > Just wondering if there is any way to have pins that vary depending upon
> > what device you are connecting to.   Currently, I just use
> > /etb/bluetooth/givepin to supply a pin, but this pin must be the same
> > for every device that my Linux laptop connects to.
> 
> this is a planned future for the new security manager which also
> includes one-time PIN codes.
> 
> For the current version you must do it by yourself in a pin-helper
> script. The BD_ADDR of the remote device is one of the parameters.

Do you think it might be right to leave "low level" PIN management as it
is now, via an executable helper?  It is very much the same way as
kernel "hotplug" works.  So it can stay the same even if hcid eventually
becomes a kernel thread.

The "real" PIN management, with the database, GUI prompt boxes etc.
could be isolated from the BT stack, helper executable being the only
interface.

E.g., a Gnome or KDE applet could listen on a unix domain socket.  The
helper, when invoked, would try to talk over this socket, and if the
latter is not present or nobody listens on it, default to preexisting
database.  This way, both fancy GUI dialogues and unattended operation
could be implemented rather easily.

Sorry if I say stupid or trivial things, I did not really try to learn
how these things are currently done in Blues..

Eugene