public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: nirav rabara <niravrabara@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Right way of pairing?
Date: Mon, 30 Nov 2009 11:47:21 +0530	[thread overview]
Message-ID: <912bb79a0911292217w10dbbf2bpbbd4e0326982d769@mail.gmail.com> (raw)
In-Reply-To: <912bb79a0911292030m7bdbe03w744145e4d16f6a68@mail.gmail.com>

I forgot to tell that, for headset device paring, I have hard coded
the pin code  "0000" in bluetoothd.

Now  If I open RFCOM socket connection, connect with another device,
then close that RFCOM socket, Will bluetoothd remove all the pairing
information from the linkkeys file or not.

Because When I close RFCOM connection pairing information is getting
lost, I would like to know weather it's a common or am I doing
something wrong??

Your suggestion would be a great help for me..



-- 
With Regards,
Nirav Rabara

      reply	other threads:[~2009-11-30  6:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28  5:52 Right way of pairing? nirav rabara
2009-11-28 16:40 ` Pierre Ficheux
2009-11-30  4:30   ` nirav rabara
2009-11-30  6:17     ` nirav rabara [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=912bb79a0911292217w10dbbf2bpbbd4e0326982d769@mail.gmail.com \
    --to=niravrabara@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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