[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169420622493.6163.1195791709998663185.git-patchwork-notify@kernel.org>
Date: Fri, 08 Sep 2023 20:50:24 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Ying Hsu <yinghsu@...omium.org>
Cc: linux-bluetooth@...r.kernel.org, marcel@...tmann.org,
chromeos-bluetooth-upstreaming@...omium.org,
johan.hedberg@...il.com, luiz.dentz@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Bluetooth: Avoid redundant authentication
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Thu, 7 Sep 2023 04:39:34 +0000 you wrote:
> While executing the Android 13 CTS Verifier Secure Server test on a
> ChromeOS device, it was observed that the Bluetooth host initiates
> authentication for an RFCOMM connection after SSP completes.
> When this happens, some Intel Bluetooth controllers, like AC9560, would
> disconnect with "Connection Rejected due to Security Reasons (0x0e)".
>
> Historically, BlueZ did not mandate this authentication while an
> authenticated combination key was already in use for the connection.
> This behavior was changed since commit 7b5a9241b780
> ("Bluetooth: Introduce requirements for security level 4").
> So, this patch addresses the aforementioned disconnection issue by
> restoring the previous behavior.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: Avoid redundant authentication
https://git.kernel.org/bluetooth/bluetooth-next/c/4c8a783f3882
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists