From: Andrejs Hanins <andrejs.hanins@ubnt.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: DBus API for LTK OOB keys
Date: Thu, 21 May 2015 10:38:52 +0300 [thread overview]
Message-ID: <555D8B8C.4090007@ubnt.com> (raw)
In-Reply-To: <280B8CCC-6E98-477A-B805-D91966220207@holtmann.org>
Hi Marcel,
On 03/06/2015 12:08 AM, Marcel Holtmann wrote:
>
> So LE Legacy Pairing needs the Security Manager TK value and LE Secure Connections needs the Confirmation and Random values. However right now, we can not get these ones from the kernel.
>
> As a side note, I added tools/oobtest utility where you can test this between two controllers attached to the same host.
Based on oobtest/kernel code/mgmt-api comments, the OOB LE legacy pairing is still not supported: "Currently there is no support for providing the Security Manager TK Value for LE legacy pairing".
Is there any plan to support it? Maybe some patches exist? Are there any serious technical difficulties behind the absence of this functionality?
I know that BT 4.2 SC provides better alternatives for secure pairing, but the 4.2 is not so widely adopted as 4.0 and our BT chip also don't support 4.2...
>
> Regards
>
> Marcel
>
next prev parent reply other threads:[~2015-05-21 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 13:21 DBus API for LTK OOB keys Andrejs Hanins
2015-03-05 13:40 ` Johan Hedberg
2015-03-05 14:05 ` Andrejs Hanins
2015-03-05 14:55 ` Marcel Holtmann
2015-03-05 20:11 ` Andrejs Hanins
2015-03-05 22:08 ` Marcel Holtmann
2015-03-06 17:54 ` Andrejs Hanins
2015-05-21 7:38 ` Andrejs Hanins [this message]
2015-05-21 12:12 ` Marcel Holtmann
2015-05-21 12:57 ` Andrejs Hanins
2015-05-21 13:10 ` Marcel Holtmann
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=555D8B8C.4090007@ubnt.com \
--to=andrejs.hanins@ubnt.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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