Linux bluetooth development
 help / color / mirror / Atom feed
From: Andy <andy@thebmwz3.co.uk>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Pairing without dbus
Date: Fri, 30 Mar 2007 16:25:54 +0100	[thread overview]
Message-ID: <460D2C02.80705@thebmwz3.co.uk> (raw)
In-Reply-To: <e1effdeb0703300454m427fa672j19fd455b78544352@mail.gmail.com>



Claudio Takahasi wrote:
> On 3/29/07, Andy <andy@thebmwz3.co.uk> wrote:
>> Hi All,
>> I'm having some major problems on a CF-based linux system based on Debian.
>> Basically, I need to do a pairing without using DBUS/passkey-agent, so
>> want to somehow populate the linkkeys file manually.
>> Can anyone advise on how to do this? (I have the address of the device,
>> and the pin it requires to pair).
>>
>> The reason is that on the basic install I've got bluetooth utils are
>> broken, and without compilers, etc I cannot build working copies, so
>> continually get:
>>
>> Mar 29 17:20:29 voyage hcid[3247]: pin_code_request
>> (sba=00:15:83:xx:xx:xx, dba=00:80:37:xx:xx:xx)
>> Mar 29 17:20:29 voyage hcid[3247]: Calling PasskeyAgent.Request:
>> name=:1.6, path=/org/bluez/passke
>> Mar 29 17:20:29 voyage hcid[3247]: Passkey agent replied with an error:
>> org.freedesktop.DBus.Errorhod "Request" with signature "ss" on interface
>> "org.bluez.PasskeyAgent" doesn't exist
>>
>>
>> Can anyone advise on how to generate the linkkeys file manually? It's
>> the 128-bit code that I've not found the information on how to create!

> The following link contains a detailed explanation how passkey agent
> works. I added some info about the HCI events flow too, it can be
> useful to understand the relation between the HCI events and the
> passkey agent interaction.
> 
> http://wiki.bluez.org/wiki/Security
> 
> You can't generate the link manually, you have to send a passkey to
> the host controller and  receives a link key notification event.


Thanks for the info Claudio, actually I managed to achieve my goal in a 
slightly odd way, which I'll document here for list searches etc.


I took the bluetooth USB hardware out of the machine I'm trying to pair 
with (the CF-based system) and plugged it into a laptop running a 
similar Debian install (which I knew had working pin applications, dbus, 
etc)
Installed bluez, drivers, etc then searched for the device.
Found it, and tried to connect, it prompted me for a pin which I gave, 
and it did a succesfull pairing with the device.

I then viewed the /var/lib/bluetooth/00:15:83:xx:xx:xx/linkkeys
and found the line that had just been created. Copied it over to the 
CF-based system, plugged the USB bluetooth device back in and it worked 
first time:
Mar 30 12:37:46 voyage hcid[2917]: link_key_request 
(sba=00:15:83:xx:xx:xx, dba=00:80:37:xx:xx:xx)
and continued to let me talk to the bluetooth device.

Regards,

-- 
Andy
e: andy @ thebmwz3.co.uk
e: andy @ broadcast-tech.co.uk
w: http://www.thebmwz3.co.uk
w: http://www.broadcast-tech.co.uk

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-03-30 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 20:43 [Bluez-users] Pairing without dbus Andy
2007-03-30 11:54 ` Claudio Takahasi
2007-03-30 15:25   ` Andy [this message]

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=460D2C02.80705@thebmwz3.co.uk \
    --to=andy@thebmwz3.co.uk \
    --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