Linux bluetooth development
 help / color / mirror / Atom feed
From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: SMP: Fix setting unknown auth_req bits
Date: Thu, 11 Oct 2012 17:34:03 +0300	[thread overview]
Message-ID: <20121011143355.GA28051@aemeltch-MOBL1> (raw)
In-Reply-To: <1349965566-29482-1-git-send-email-johan.hedberg@gmail.com>

Hi Johan,

On Thu, Oct 11, 2012 at 04:26:06PM +0200, Johan Hedberg wrote:
> From: Johan Hedberg <johan.hedberg@intel.com>
> 
> When sending a pairing request or response we should not just blindly
> copy the value that the remote device sent. Instead we should at least
> make sure to mask out any unknown bits. This is particularly critical
> from the upcoming LE Secure Connections feature perspective as
> incorrectly indicating support for it (by copying the remote value)
> would cause a failure to pair with devices that support it.
> 
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> Cc: stable@kernel.org
> Acked-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>  net/bluetooth/smp.c |    6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/net/bluetooth/smp.c b/net/bluetooth/smp.c
> index 9b54fea..9176bc1 100644
> --- a/net/bluetooth/smp.c
> +++ b/net/bluetooth/smp.c
> @@ -32,6 +32,8 @@
>  
>  #define SMP_TIMEOUT	msecs_to_jiffies(30000)
>  
> +#define AUTH_REQ_MASK   0x07
> +
>  static inline void swap128(u8 src[16], u8 dst[16])
>  {
>  	int i;
> @@ -230,7 +232,7 @@ static void build_pairing_cmd(struct l2cap_conn *conn,
>  		req->max_key_size = SMP_MAX_ENC_KEY_SIZE;
>  		req->init_key_dist = 0;
>  		req->resp_key_dist = dist_keys;
> -		req->auth_req = authreq;
> +		req->auth_req = (authreq & AUTH_REQ_MASK);
>  		return;
>  	}
>  
> @@ -239,7 +241,7 @@ static void build_pairing_cmd(struct l2cap_conn *conn,
>  	rsp->max_key_size = SMP_MAX_ENC_KEY_SIZE;
>  	rsp->init_key_dist = 0;
>  	rsp->resp_key_dist = req->resp_key_dist & dist_keys;
> -	rsp->auth_req = authreq;
> +	rsp->auth_req = (authreq & AUTH_REQ_MASK);

Would it be better to omit braces like in the line above? For both cases.

Best regards 
Andrei Emeltchenko 


  reply	other threads:[~2012-10-11 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 14:26 [PATCH] Bluetooth: SMP: Fix setting unknown auth_req bits Johan Hedberg
2012-10-11 14:34 ` Andrei Emeltchenko [this message]
2012-10-11 15:00   ` Johan Hedberg
2012-10-12  9:56 ` 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=20121011143355.GA28051@aemeltch-MOBL1 \
    --to=andrei.emeltchenko.news@gmail.com \
    --cc=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