Hi Johan, > 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@xxxxxxxxx> > --- > net/bluetooth/smp.c | 32 +++++++++++++++++++++++++++----- > net/bluetooth/smp.h | 3 ++- > 2 files changed, 29 insertions(+), 6 deletions(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html