linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <bgix@codeaurora.org>
To: Hemant Gupta <hemant.gupta@stericsson.com>
Cc: linux-bluetooth@vger.kernel.org,
	Naresh Gupta <naresh.gupta@stericsson.com>,
	Hemant Gupta <hemantgupta.ste@gmail.com>
Subject: Re: [PATCH-v1 1/1] Bluetooth: Incorrect address while storing LTK.
Date: Thu, 22 Dec 2011 22:28:53 -0800	[thread overview]
Message-ID: <4EF41FA5.1030903@codeaurora.org> (raw)
In-Reply-To: <1324618644-17551-2-git-send-email-hemant.gupta@stericsson.com>

Hi Hemant,

On 12/22/2011 9:37 PM, Hemant Gupta wrote:
> This patch fixes incorrect address storage while storing
> Long Term Key for LE Devices using SMP (Security Manager Protocol).
> The address stored should be of remote device and not of source device.
>
> Signed-off-by: Hemant Gupta<hemant.gupta@stericsson.com>
> ---
>   net/bluetooth/smp.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/bluetooth/smp.c b/net/bluetooth/smp.c
> index 9fea4bf..32c47de 100644
> --- a/net/bluetooth/smp.c
> +++ b/net/bluetooth/smp.c
> @@ -820,7 +820,7 @@ static int smp_cmd_master_ident(struct l2cap_conn *conn, struct sk_buff *skb)
>
>   	skb_pull(skb, sizeof(*rp));
>
> -	hci_add_ltk(conn->hcon->hdev, 1, conn->src, smp->smp_key_size,
> +	hci_add_ltk(conn->hcon->hdev, 1, conn->dst, smp->smp_key_size,
>   						rp->ediv, rp->rand, smp->tk);
>
>   	smp_distribute_keys(conn, 1);

I agree that this is a bug, and that this is the correct fix.


-- 
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

  reply	other threads:[~2011-12-23  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23  5:37 [PATCH-v1 0/1] Bluetooth: Incorrect address while storing LTK Hemant Gupta
2011-12-23  5:37 ` [PATCH-v1 1/1] " Hemant Gupta
2011-12-23  6:28   ` Brian Gix [this message]
2011-12-23  7:37   ` Marcel Holtmann
2011-12-23 18:55   ` Gustavo Padovan

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=4EF41FA5.1030903@codeaurora.org \
    --to=bgix@codeaurora.org \
    --cc=hemant.gupta@stericsson.com \
    --cc=hemantgupta.ste@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=naresh.gupta@stericsson.com \
    /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).