From: Ajay <ajay.kv@globaledgesoft.com>
To: linux-bluetooth@vger.kernel.org
Subject: BLE : SMP pairing + LE_Start_encryption
Date: Thu, 29 Nov 2012 02:57:35 +0530 [thread overview]
Message-ID: <50B681C7.1030207@globaledgesoft.com> (raw)
Hi,
how do i do smp pairing and ltk key distribution using l2cap socket
connection? does bluez provide any tools for LE pairing . my ultimate
result should be enabling LE_start_encryption , which requires ltk key
distribution (which is a part of LE_pairing).
spec 4.0 says we can use l2cap cid 0x06 , defined for this purpose
(smp pairing) . But when i used cid =0x06 , l2cap connect creates an
normal acl connection with cid = 40 , which doesnt trigger any smp
modules at remote side.
please look into this issue.
--
Thanks & regards
AJAY KV
GlobalEdge software Ltd
8892753703
next reply other threads:[~2012-11-28 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 21:27 Ajay [this message]
2012-11-30 12:08 ` BLE : SMP pairing + LE_Start_encryption Anderson Lizardo
2012-11-29 0:35 ` Ajay
2012-11-30 12:53 ` Anderson Lizardo
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=50B681C7.1030207@globaledgesoft.com \
--to=ajay.kv@globaledgesoft.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;
as well as URLs for NNTP newsgroup(s).