linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: Fix SMP security elevation from medium to high
Date: Fri, 8 Jun 2012 04:19:33 -0300	[thread overview]
Message-ID: <20120608071933.GE1546@joana> (raw)
In-Reply-To: <1339052318-11423-2-git-send-email-johan.hedberg@gmail.com>

Hi Johan,

* Johan Hedberg <johan.hedberg@gmail.com> [2012-06-07 14:58:37 +0800]:

> From: Johan Hedberg <johan.hedberg@intel.com>
> 
> If we have an unauthenticated key it is not sufficient to acheive high
> security. Therefore, when deciding whether to encrypt the link or
> request pairing, it is essential to in addition to checking the
> existence of a key to also check whether it is authenticated or not.
> 
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
>  net/bluetooth/smp.c |    9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)

Patch has been applied to bluetooth.git. Thanks.

	Gustavo

  reply	other threads:[~2012-06-08  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  6:58 [PATCH 0/2] Bluetooth: Fix SMP support for encryption key refresh Johan Hedberg
2012-06-07  6:58 ` [PATCH 1/2] Bluetooth: Fix SMP security elevation from medium to high Johan Hedberg
2012-06-08  7:19   ` Gustavo Padovan [this message]
2012-06-07  6:58 ` [PATCH 2/2] Bluetooth: Add support for encryption key refresh Johan Hedberg
2012-06-07  7:07   ` Andrei Emeltchenko
2012-06-07  7:14     ` Johan Hedberg
2012-06-07  7:25       ` Andrei Emeltchenko
2012-06-08  7:20   ` Gustavo Padovan
2012-06-08 15:31     ` [PATCH v2] " Johan Hedberg
2012-06-09  0:12       ` 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=20120608071933.GE1546@joana \
    --to=gustavo@padovan.org \
    --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;
as well as URLs for NNTP newsgroup(s).