From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org, Johan Hedberg <johan.hedberg@nokia.com>
Subject: Re: [PATCH] Bluetooth: Fix initial RFCOMM DLC security level
Date: Mon, 6 Dec 2010 16:34:49 +0200 [thread overview]
Message-ID: <AANLkTin-GeijFDGrkBSBDJkEJmqaindzuJs3k7cN-fdu@mail.gmail.com> (raw)
In-Reply-To: <1291643777-18851-1-git-send-email-johan.hedberg@gmail.com>
Hi,
On Mon, Dec 6, 2010 at 3:56 PM, <johan.hedberg@gmail.com> wrote:
> From: Johan Hedberg <johan.hedberg@nokia.com>
>
> Due to commit 63ce0900 connections initiated through TTYs created with
> "rfcomm bind ..." would have security level BT_SECURITY_SDP instead of
> BT_SECURITY_LOW. This would cause instant connection failure between any
> two SSP capable devices due to the L2CAP connect request to RFCOMM being
> sent before authentication has been performed. This patch fixes the
> regression by always initializing the DLC security level to
> BT_SECURITY_LOW.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@nokia.com>
> ---
> net/bluetooth/rfcomm/core.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/net/bluetooth/rfcomm/core.c b/net/bluetooth/rfcomm/core.c
> index fa642aa..432a9a6 100644
> --- a/net/bluetooth/rfcomm/core.c
> +++ b/net/bluetooth/rfcomm/core.c
> @@ -311,6 +311,7 @@ static void rfcomm_dlc_clear_state(struct rfcomm_dlc *d)
> d->state = BT_OPEN;
> d->flags = 0;
> d->mscex = 0;
> + d->sec_level = BT_SECURITY_LOW;
> d->mtu = RFCOMM_DEFAULT_MTU;
> d->v24_sig = RFCOMM_V24_RTC | RFCOMM_V24_RTR | RFCOMM_V24_DV;
>
Nice catch, I completely forgot to check if tty initialize sec_level
with anything.
Acked-by: Luiz Augusto von Dentz <luiz.dentz-von@nokia.com>
--
Luiz Augusto von Dentz
Computer Engineer
next prev parent reply other threads:[~2010-12-06 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 13:56 [PATCH] Bluetooth: Fix initial RFCOMM DLC security level johan.hedberg
2010-12-06 14:34 ` Luiz Augusto von Dentz [this message]
2010-12-06 17:53 ` Gustavo F. 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=AANLkTin-GeijFDGrkBSBDJkEJmqaindzuJs3k7cN-fdu@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=johan.hedberg@nokia.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).