From: patchwork-bot+bluetooth@kernel.org
To: Oleh Konko <security@1seal.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Bluetooth: SMP: honor local MITM requirements for legacy pairing
Date: Wed, 01 Apr 2026 19:10:04 +0000 [thread overview]
Message-ID: <177507060479.3825986.13933762022782579575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <bt-smp-v4-ea63d24bfcd1416f9da279190fab15fc@1seal.org>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 31 Mar 2026 11:52:12 +0000 you wrote:
> hi,
>
> this v4 series follows up on Luiz's latest review direction.
>
> 1/2 moves the primary fix into smp_cmd_pairing_req(): when the local
> side requires BT_SECURITY_HIGH, the responder first verifies that MITM
> is achievable and then forces SMP_AUTH_MITM in the pairing response so
> the responder auth bits and later method selection stay aligned.
>
> [...]
Here is the summary with links:
- [v4,1/2] Bluetooth: SMP: force responder MITM requirements before building the pairing response
(no matching commit)
- [v4,2/2] Bluetooth: SMP: derive legacy responder STK authentication from MITM state
https://git.kernel.org/bluetooth/bluetooth-next/c/3a0b100b337c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-01 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 11:52 [PATCH v4 0/2] Bluetooth: SMP: honor local MITM requirements for legacy pairing Oleh Konko
2026-03-31 11:52 ` [PATCH v4 1/2] Bluetooth: SMP: force responder MITM requirements before building the pairing response Oleh Konko
2026-03-31 13:25 ` Bluetooth: SMP: honor local MITM requirements for legacy pairing bluez.test.bot
2026-03-31 11:52 ` [PATCH v4 2/2] Bluetooth: SMP: derive legacy responder STK authentication from MITM state Oleh Konko
2026-04-01 19:10 ` patchwork-bot+bluetooth [this message]
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=177507060479.3825986.13933762022782579575.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=security@1seal.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