From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] How to initiate a Pin-Exchange?
Date: Thu, 15 Apr 2004 22:21:06 +0200 [thread overview]
Message-ID: <20040415202106.GA17934@gmx.net> (raw)
In-Reply-To: <200404151729.32798.cijoml@volny.cz>
On 0, "Michal Semler (volny.cz)" <cijoml@volny.cz> wrote:
> Dne ?t 15. dubna 2004 11:49 Benoit Panizzon napsal(a):
> > > How can I start the pin exchange with bluez?
> > > > bluez-pin does nothing at all as I see with hcidump.
> > >
> > > It's used when second site request pin when connecting
> >
> > Ok, but how do I request a pin from another device with bluez? Like when I
> > got a bluez-bluez setup?
>
> I never needed that. I allways tried connect to remote side and second device
> allways requested for pin :)
The archive is down at the moment, so i can't look the history of this
thread but I hope my asumptions aren't that wrong.
If you try to connect from a bluez-computer to any other device, it
should etablish a connection. The stack should notice that there is need
for a link key and if none exists it requests a pin.
< HCI Command: Create Connection(0x01|0x0005) plen 13
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: Link Key Request(0x17) plen 6
< HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
> HCI Event: Command Complete(0x0e) plen 10
> HCI Event: PIN Code Request(0x16) plen 6
< HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23
> HCI Event: Command Complete(0x0e) plen 10
> HCI Event: Link Key Notification(0x18) plen 23
> HCI Event: Connect Complete(0x03) plen 11
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
> HCI Event: Command Complete(0x0e) plen 6
I etablished the connection with hcitool. Which prints an timeout but
completes the connection as requested.
nicholas
P.S.: I noticed that bluez-pin only get the correct xauth credentials
when the bluetooth userland daemons are restarted after X is up.
Unfortunately I understand nothing from the X Authentication system, so
i have no clue why or how to fix it.
Kernel 2.6.5-mh3
bluez-libs 2.6
bluez-utils 2.6
bluez-pin 0.23
AUTH ENCRYPT
and hcid.conf: "security user;"
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-04-15 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 20:03 [Bluez-users] How to initiate a Pin-Exchange? Benoit Panizzon
2004-04-14 20:11 ` Michal Semler (volny.cz)
2004-04-15 9:49 ` Benoit Panizzon
2004-04-15 15:29 ` Michal Semler (volny.cz)
2004-04-15 20:21 ` Nicholas A. Preyss [this message]
2004-04-17 0:08 ` Marcel Holtmann
2004-04-17 14:03 ` Nicholas A. Preyss
2004-04-18 9:25 ` Marcel Holtmann
2004-04-17 0:04 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040415202106.GA17934@gmx.net \
--to=nalp@gmx.net \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox