public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralph Hempel <rhempel@hempeldesigngroup.com>
To: Nel D <newatlinux@gmail.com>
Cc: Ed Tsang <netdesign_98@yahoo.com>,
	Bluettooth Linux <linux-bluetooth@vger.kernel.org>
Subject: Re: How to force a fix pin
Date: Wed, 09 Dec 2009 08:20:15 -0500	[thread overview]
Message-ID: <4B1FA40F.2020003@hempeldesigngroup.com> (raw)
In-Reply-To: <e378cfb20912090123m51645679n3e410d6208c6f51e@mail.gmail.com>

Nel D wrote:
> Hi ,
> 
> 
> On Wed, Dec 9, 2009 at 3:45 AM, Ed Tsang <netdesign_98@yahoo.com> wrote:
>> Hi, My application scan for devices, send file to it. But some device (blackberry) will request a pin. With the bluetoothd 4.51. bluetooth-applet will pop up and enter a pin. If de-install it, the bluetoothd will complain "No agent available for 0 request (pin_code_request?).". And the remote device failed to pair with a "default pin 0000".
>> Is there a way to force a default pin "0000".  look like /etc/bluetooth/pin is history.  Is there a simply work around.
>>
>> Net Des

In the directory /var/lib/xx:yy:xx:yy:xx:yy/

where xx:yy:xx:yy:xx:yy is your Bluetooth interface MAC

you will either find or have to create two files:

pincodes
trusts

Assuming that your other device is aa:bb:aa:bb:aa:bb you
modify the files as follows:

In the pincodes file, add a line like this, replace 0000
with your desired pincode

aa:bb:aa:bb:aa:bb 0000

In the trusts file, put this:

aa:bb:aa:bb:aa:bb [all]

Which says the device can access all services (I think)

If the pairing is sucessful you will get a new
entry in the linkkeys file, and that key will then be
used in the future, so no more pairing is required.

I am currently investigating why (in 4.57) the linkkeys
and trusts entry of a successfully paired device are
sometimes deleted.

Ralph


  reply	other threads:[~2009-12-09 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 22:15 How to force a fix pin Ed Tsang
2009-12-09  9:23 ` Nel D
2009-12-09 13:20   ` Ralph Hempel [this message]
2009-12-09 13:21     ` Ralph Hempel
2009-12-09 15:04     ` Ed Tsang
2009-12-09 17:49       ` Ralph Hempel
2009-12-09 19:09         ` Ed Tsang

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=4B1FA40F.2020003@hempeldesigngroup.com \
    --to=rhempel@hempeldesigngroup.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=netdesign_98@yahoo.com \
    --cc=newatlinux@gmail.com \
    /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