From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix SMP authentication requirement when initiator
Date: Tue, 29 Jul 2014 14:48:12 +0300 [thread overview]
Message-ID: <20140729114812.GA26881@t440s.lan> (raw)
In-Reply-To: <1406624859-17294-1-git-send-email-johan.hedberg@gmail.com>
On Tue, Jul 29, 2014, johan.hedberg@gmail.com wrote:
> Even if we're not pairable (the HCI_PAIRABLE flag is unset) we should
> still allow initiating pairing with bonding. This patch adds a missing
> check for SMP_FLAG_INITIATOR to build_pairing_cmd() and ensures this
> flag is properly set before calling the function.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> net/bluetooth/smp.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/net/bluetooth/smp.c b/net/bluetooth/smp.c
> index a7c344b4acbc..7e914477721a 100644
> --- a/net/bluetooth/smp.c
> +++ b/net/bluetooth/smp.c
> @@ -307,7 +307,8 @@ static void build_pairing_cmd(struct l2cap_conn *conn,
> struct hci_dev *hdev = hcon->hdev;
> u8 local_dist = 0, remote_dist = 0;
>
> - if (test_bit(HCI_PAIRABLE, &conn->hcon->hdev->dev_flags)) {
> + if (test_bit(HCI_PAIRABLE, &conn->hcon->hdev->dev_flags) ||
> + test_bit(SMP_FLAG_INITIATOR, &smp->flags)) {
> local_dist = SMP_DIST_ENC_KEY | SMP_DIST_SIGN;
> remote_dist = SMP_DIST_ENC_KEY | SMP_DIST_SIGN;
> authreq |= SMP_AUTH_BONDING;
> @@ -985,6 +986,8 @@ int smp_conn_security(struct hci_conn *hcon, __u8 sec_level)
> hcon->pending_sec_level > BT_SECURITY_MEDIUM)
> authreq |= SMP_AUTH_MITM;
>
> + set_bit(SMP_FLAG_INITIATOR, &smp->flags);
> +
> if (hcon->role == HCI_ROLE_MASTER) {
> struct smp_cmd_pairing cp;
>
> @@ -999,8 +1002,6 @@ int smp_conn_security(struct hci_conn *hcon, __u8 sec_level)
> smp_send_cmd(conn, SMP_CMD_SECURITY_REQ, sizeof(cp), &cp);
> }
>
> - set_bit(SMP_FLAG_INITIATOR, &smp->flags);
> -
> return 0;
> }
Hold on with this patch for a bit. There are some SM test cases that
require us to be able to initiate no-bonding pairing (e.g.
TP/JW/BV-01-C). So we have to retain somehow the capability of doing
this.
A simple solution would be to revert bluez.git back to always enabling
pairable and then forget about this kernel patch.
Johan
next prev parent reply other threads:[~2014-07-29 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 9:07 [PATCH] Bluetooth: Fix SMP authentication requirement when initiator johan.hedberg
2014-07-29 11:48 ` Johan Hedberg [this message]
2014-07-29 12:39 ` Johan Hedberg
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=20140729114812.GA26881@t440s.lan \
--to=johan.hedberg@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;
as well as URLs for NNTP newsgroup(s).