From: johan.hedberg@gmail.com
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v2 0/4] Bluetooth: Fix initiator/responder addresses for SMP
Date: Fri, 28 Feb 2014 12:54:13 +0200 [thread overview]
Message-ID: <1393584857-30375-1-git-send-email-johan.hedberg@gmail.com> (raw)
Hi,
Here's a second attempt to fix the initiator/responder addresses when
using privacy. The main difference to the previous attempt is an added
protection to HCI_Set_Random_Address so we don't do that while
connecting or advertising, and a clarification for the white list corner
case in aptch 3/4 that we're taking a "best effort" approach while
lacking full tracking of white list initiated connections.
Johan
----------------------------------------------------------------
Johan Hedberg (4):
Bluetooth: Add protections for updating local random address
Bluetooth: Fix updating connection state to BT_CONNECT too early
Bluetooth: Track LE initiator and responder address information
Bluetooth: Use hdev->init/resp_addr values for smp_c1 function
include/net/bluetooth/hci_core.h | 4 ++
net/bluetooth/hci_conn.c | 3 +-
net/bluetooth/hci_core.c | 27 ++++++++++++-
net/bluetooth/hci_event.c | 78 ++++++++++++++++++++++++++++++++++++
net/bluetooth/mgmt.c | 7 ++++
net/bluetooth/smp.c | 22 +++-------
6 files changed, 122 insertions(+), 19 deletions(-)
next reply other threads:[~2014-02-28 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 10:54 johan.hedberg [this message]
2014-02-28 10:54 ` [PATCH v2 1/4] Bluetooth: Add protections for updating local random address johan.hedberg
2014-02-28 10:54 ` [PATCH v2 2/4] Bluetooth: Fix updating connection state to BT_CONNECT too early johan.hedberg
2014-02-28 10:54 ` [PATCH v2 3/4] Bluetooth: Track LE initiator and responder address information johan.hedberg
2014-02-28 10:54 ` [PATCH v2 4/4] Bluetooth: Use hdev->init/resp_addr values for smp_c1 function johan.hedberg
2014-02-28 15:54 ` [PATCH v2 0/4] Bluetooth: Fix initiator/responder addresses for SMP Marcel Holtmann
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=1393584857-30375-1-git-send-email-johan.hedberg@gmail.com \
--to=johan.hedberg@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox