Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-565-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v3] Bluetooth: Add more enc key size check
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170239862337.27856.15531627573114071096.git-patchwork-notify@kernel.org>
Date: Tue, 12 Dec 2023 16:30:23 +0000
References: <ZXfFyoEhCj_S70qp@alexlu>
In-Reply-To: <ZXfFyoEhCj_S70qp@alexlu>
To: Alex Lu <alex_lu@realsil.com.cn>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com,
 linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
 max.chou@realtek.com, karenhsu@realtek.com

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 12 Dec 2023 10:30:34 +0800 you wrote:
> From: Alex Lu <alex_lu@realsil.com.cn>
> 
> When we are slave role and receives l2cap conn req when encryption has
> started, we should check the enc key size to avoid KNOB attack or BLUFFS
> attack.
> From SIG recommendation, implementations are advised to reject
> service-level connections on an encrypted baseband link with key
> strengths below 7 octets.
> A simple and clear way to achieve this is to place the enc key size
> check in hci_cc_read_enc_key_size()
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: Add more enc key size check
    https://git.kernel.org/bluetooth/bluetooth-next/c/19921189d442

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html