Bluetooth: Re-encrypt link after receiving an LTK

Browse source

It's not strictly speaking required to re-encrypt a link once we receive
an LTK since the connection is already encrypted with the STK. However,
re-encrypting with the LTK allows us to verify that we've received an
LTK that actually works.

This patch updates the SMP code to request encrypting with the LTK in
case we're in master role and waits until the key refresh complete event
before notifying user space of the distributed keys.

A new flag is also added for the SMP context to ensure that we
re-encryption only once in case of multiple calls to smp_distribute_keys.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

...

This commit is contained in:

Johan Hedberg 2014-02-28 18:10:02 +02:00 • committed by Marcel Holtmann

parent 9489eca4ab

commit 38ccdc9332

2 changed files with 29 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

32

net/bluetooth/smp.c

View file

3

net/bluetooth/smp.h

View file