linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] Bluetooth: Check key sizes only when Secure Simple Pairing is enabled
Date: Thu, 23 May 2019 07:53:47 -0700	[thread overview]
Message-ID: <CA+E=qVcW0aQ=D_0bvEbTL9VA5P_2iykbZpNr2xH8P-eHB3FSog@mail.gmail.com> (raw)
In-Reply-To: <20190522070540.48895-1-marcel@holtmann.org>

On Wed, May 22, 2019 at 12:05 AM Marcel Holtmann <marcel@holtmann.org> wrote:
>
> The encryption is only mandatory to be enforced when both sides are using
> Secure Simple Pairing and this means the key size check makes only sense
> in that case.
>
> On legacy Bluetooth 2.0 and earlier devices like mice the encryption was
> optional and thus causing an issue if the key size check is not bound to
> using Secure Simple Pairing.
>
> Fixes: d5bb334a8e17 ("Bluetooth: Align minimum encryption key size for LE and BR/EDR connections")
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> Cc: stable@vger.kernel.org

Tested-by: Vasily Khoruzhick <anarsoul@gmail.com>

> ---
>  net/bluetooth/hci_conn.c | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
> index 3cf0764d5793..7516cdde3373 100644
> --- a/net/bluetooth/hci_conn.c
> +++ b/net/bluetooth/hci_conn.c
> @@ -1272,8 +1272,13 @@ int hci_conn_check_link_mode(struct hci_conn *conn)
>                         return 0;
>         }
>
> -       if (hci_conn_ssp_enabled(conn) &&
> -           !test_bit(HCI_CONN_ENCRYPT, &conn->flags))
> +       /* If Secure Simple Pairing is not enabled, then legacy connection
> +        * setup is used and no encryption or key sizes can be enforced.
> +        */
> +       if (!hci_conn_ssp_enabled(conn))
> +               return 1;
> +
> +       if (!test_bit(HCI_CONN_ENCRYPT, &conn->flags))
>                 return 0;
>
>         /* The minimum encryption key size needs to be enforced by the
> --
> 2.20.1
>

  reply	other threads:[~2019-05-23 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  7:05 [RFC] Bluetooth: Check key sizes only when Secure Simple Pairing is enabled Marcel Holtmann
2019-05-23 14:53 ` Vasily Khoruzhick [this message]
2019-06-04 12:26   ` Bastien Nocera

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='CA+E=qVcW0aQ=D_0bvEbTL9VA5P_2iykbZpNr2xH8P-eHB3FSog@mail.gmail.com' \
    --to=anarsoul@gmail.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;
as well as URLs for NNTP newsgroup(s).