From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: L2CAP: Hold incoming data until encryption key size is known
Date: Fri, 23 Oct 2026 21:00:34 +0000 [thread overview]
Message-ID: <179278923481.1268720.9107027824998220837.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261022154621.3958803-2-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 22 Oct 2026 11:46:21 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Once encryption is enabled on an ACL link, the encryption key size is
> read from the controller, using hdev->min_enc_key_size in the meantime.
> Data received before the reply is processed with that key size, so a
> peer starting SMP over BR/EDR right after encryption, which it may do,
> gets its Pairing Request rejected with "Encryption Key Size" whenever
> the pending security level is FIPS, as that requires a 16 octet key:
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: L2CAP: Hold incoming data until encryption key size is known
https://git.kernel.org/bluetooth/bluetooth-next/c/2aa8a39c5a81
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-23 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:46 [PATCH v1] Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI Luiz Augusto von Dentz
2026-10-22 15:46 ` [PATCH v1] Bluetooth: L2CAP: Hold incoming data until encryption key size is known Luiz Augusto von Dentz
2026-10-22 18:20 ` [v1] " bluez.test.bot
2026-10-23 21:00 ` patchwork-bot+bluetooth [this message]
2026-10-22 18:08 ` [v1] Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI bluez.test.bot
2026-10-23 21:00 ` [PATCH v1] " patchwork-bot+bluetooth
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=179278923481.1268720.9107027824998220837.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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