From: Brian Gix <bgix@codeaurora.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH-v3 0/9] Bluetooth: Add MITM protection to LE-SMP
Date: Wed, 16 Nov 2011 10:37:44 -0800 [thread overview]
Message-ID: <1321468673-13925-1-git-send-email-bgix@codeaurora.org> (raw)
This is a resend of last nights patch's to address Gustavo's
confusion over the Patch Revision. I have relabeled these as
Patch version "3" to account for them being the third set, although
I had not ever correctly labeled anything as Patch revision "2".
The rest of Gustavo's comments were essentially the same as Marcel's,
which were to address sparseness and in some cases lack of commit
messages.
Re-Including the the other cover page info below:
This patch set is nearly identical to the previous patchset, except
that I added MGMT_EV_USER_PASSKEY_REQUEST, and related functions
to make more fully symmetric with MGMT_EV_USER_CONFIRM_REQUEST.
Otherwise, more of the same, and the rest of my original connects apply:
This patch set addresses all the issues that I saw raised. The
first two are the header only changes previously Acked by Marcel.
The main MGMT changes are in patch 3 and 4. Patch 3 restructures
the User Pairing input without adding any functionality. Patch 4
adds in the Passkey entry, in the style introduced in 3, reusing
the shared common code.
Patch 5 handles the Passkey Request event, and the Cmd Cmplt events
generated by the Passkey Response commands.
Patches 6 and 7 clean-up some issues in SMP that could leak memory,
and complete notification to User space of pairing failures.
In patch 8, we have the actual addition of the MITM changes for SMP,
with calls into MGMT to obtain Passkeys and/or Confirmations.
Patch 9 adds the calls back into SMP with Passkey/Confirmation results.
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next reply other threads:[~2011-11-16 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 18:37 Brian Gix [this message]
2011-11-16 18:37 ` [PATCH-v3 1/9] Bluetooth: Add HCI defines for User Passkey entry Brian Gix
2011-11-16 18:37 ` [PATCH-v3 2/9] Bluetooth: Add MGMT opcodes for Passkey Entry Brian Gix
2011-11-16 18:51 ` Gustavo Padovan
2011-11-16 18:37 ` [PATCH-v3 3/9] Bluetooth: User Pairing Response restructuring Brian Gix
2011-11-16 18:37 ` [PATCH-v3 4/9] Bluetooth: Add User Passkey Response handling Brian Gix
2011-11-16 18:37 ` [PATCH-v3 5/9] Bluetooth: Add HCI User Passkey Req Evt handling Brian Gix
2011-11-16 18:37 ` [PATCH-v3 6/9] Bluetooth: Cleanup blkcipher on SMP termination Brian Gix
2011-11-16 18:37 ` [PATCH-v3 7/9] Bluetooth: Centralize SMP pairing failure handling Brian Gix
2011-11-16 18:37 ` [PATCH-v3 8/9] Bluetooth: Add MITM mechanism to LE-SMP Brian Gix
2011-11-16 18:37 ` [PATCH-v3 9/9] Bluetooth: Add SMP to User Passkey and Confirm Brian Gix
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=1321468673-13925-1-git-send-email-bgix@codeaurora.org \
--to=bgix@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.