* [Bluez-devel] Device specific pins
@ 2004-01-26 21:44 Dave Henriksen
2004-01-26 21:10 ` Marcel Holtmann
0 siblings, 1 reply; 5+ messages in thread
From: Dave Henriksen @ 2004-01-26 21:44 UTC (permalink / raw)
To: BlueZ Mailing List
Hi,
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.
Thanks,
Dave Henriksen
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bluez-devel] Device specific pins
2004-01-26 21:44 [Bluez-devel] Device specific pins Dave Henriksen
@ 2004-01-26 21:10 ` Marcel Holtmann
[not found] ` <1075157711.3751.1.camel@linux.local>
2004-01-27 7:05 ` Eugene Crosser
0 siblings, 2 replies; 5+ messages in thread
From: Marcel Holtmann @ 2004-01-26 21:10 UTC (permalink / raw)
To: Dave Henriksen; +Cc: BlueZ Mailing List
Hi Dave,
> 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.
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
^ permalink raw reply [flat|nested] 5+ messages in thread[parent not found: <1075157711.3751.1.camel@linux.local>]
* Re: [Bluez-devel] Device specific pins
2004-01-26 21:10 ` Marcel Holtmann
[not found] ` <1075157711.3751.1.camel@linux.local>
@ 2004-01-27 7:05 ` Eugene Crosser
2004-01-27 14:10 ` Marcel Holtmann
1 sibling, 1 reply; 5+ messages in thread
From: Eugene Crosser @ 2004-01-27 7:05 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: Dave Henriksen, BlueZ Mailing List
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Bluez-devel] Device specific pins
2004-01-27 7:05 ` Eugene Crosser
@ 2004-01-27 14:10 ` Marcel Holtmann
0 siblings, 0 replies; 5+ messages in thread
From: Marcel Holtmann @ 2004-01-27 14:10 UTC (permalink / raw)
To: Eugene Crosser; +Cc: Dave Henriksen, BlueZ Mailing List
Hi Eugene,
> 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..
the answer for all this stuff will be D-BUS.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-01-27 14:10 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-26 21:44 [Bluez-devel] Device specific pins Dave Henriksen
2004-01-26 21:10 ` Marcel Holtmann
[not found] ` <1075157711.3751.1.camel@linux.local>
2004-01-26 23:26 ` Marcel Holtmann
2004-01-27 7:05 ` Eugene Crosser
2004-01-27 14:10 ` Marcel Holtmann
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.