From: johan.hedberg@gmail.com
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/4] Bluetooth: SMP LTK fixes
Date: Thu, 30 Jan 2014 19:39:56 -0800 [thread overview]
Message-ID: <1391139600-15366-1-git-send-email-johan.hedberg@gmail.com> (raw)
Hi,
Now that my LTK key distribution patch is already applied I
unfortunately uncovered several bugs due to it. The main issue is that
the kernel code was not accounting for the possibility of there being
two LTKs for the same remote device in the hdev->long_term_keys list.
There are still fixes needed on the user space side which I haven't
completely sorted out yet (to pushable form - it's more or less working
already through). Right now the storage format doesn't allow storing two
LTKs for the same device.
----------------------------------------------------------------
Johan Hedberg (4):
Bluetooth: Fix long_term_keys debugfs output
Bluetooth: Make LTK key type check more readable
Bluetooth: Remove unnecessary LTK type check from hci_add_ltk
Bluetooth: Fix differentiating stored master vs slave LTK types
include/net/bluetooth/hci_core.h | 5 +++--
net/bluetooth/hci_core.c | 31 +++++++++++++++++++++----------
net/bluetooth/hci_event.c | 2 +-
net/bluetooth/smp.c | 3 ++-
4 files changed, 27 insertions(+), 14 deletions(-)
next reply other threads:[~2014-01-31 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 3:39 johan.hedberg [this message]
2014-01-31 3:39 ` [PATCH 1/4] Bluetooth: Fix long_term_keys debugfs output johan.hedberg
2014-01-31 3:39 ` [PATCH 2/4] Bluetooth: Make LTK key type check more readable johan.hedberg
2014-01-31 3:39 ` [PATCH 3/4] Bluetooth: Remove unnecessary LTK type check from hci_add_ltk johan.hedberg
2014-01-31 3:40 ` [PATCH 4/4] Bluetooth: Fix differentiating stored master vs slave LTK types johan.hedberg
2014-01-31 3:51 ` [PATCH 0/4] Bluetooth: SMP LTK fixes 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=1391139600-15366-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