From: Ajay <ajay.kv@globaledgesoft.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: BLE : SMP pairing + LE_Start_encryption
Date: Thu, 29 Nov 2012 06:05:51 +0530 [thread overview]
Message-ID: <50B6ADE7.3070000@globaledgesoft.com> (raw)
In-Reply-To: <CAJdJm_MCt+dep8XipFonUvRO5uoBiHNZeZm_80+LG7=E0DpTLg@mail.gmail.com>
On Friday 30 November 2012 05:38 PM, Anderson Lizardo wrote:
> Hi Ajay,
>
> On Wed, Nov 28, 2012 at 5:27 PM, Ajay <ajay.kv@globaledgesoft.com> wrote:
>>
>> 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).
>
> Either using mgmt API to do pairing (see mgmt_create_bonding() in
> src/mgmt.c from bluez sources and doc/mgmt-api.txt for how to do this)
> or increase socket security level to at least medium using
> setsockopt() (see set_sec_level() in btio/btio.c for how to do this).
>
> In summary, you will need to use BlueZ code as reference if you want
> to do these things on your own. The easier route is to use BlueZ D-Bus
> API to do pairing.
>
> Regards,
>
thanks Anderson ,
sorry if im confusing you .
is it possible to create an l2cap connection with cid 0x06 and psm 0 ?
, so that i can make use of dedicated smp-l2cap channel for data
transfer . I wanted to try how the remote device is handling on
receiving an smp_pairing_request . i have seen in l2cap_core.c , it is
getting handled inside a switch case (case cid == L2CAP_CID_SMP).
--
Thanks & regards
AJAY KV
GlobalEdge software Ltd
8892753703
next prev parent reply other threads:[~2012-11-29 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 21:27 BLE : SMP pairing + LE_Start_encryption Ajay
2012-11-30 12:08 ` Anderson Lizardo
2012-11-29 0:35 ` Ajay [this message]
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=50B6ADE7.3070000@globaledgesoft.com \
--to=ajay.kv@globaledgesoft.com \
--cc=anderson.lizardo@openbossa.org \
--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).