Re: [PATCH] Bluetooth: Don't use remote address type to decide IRK persistency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Johan,

> There are LE devices on the market that start off by announcing their
> public address and then once paired switch to using private address.
> To be interoperable with such devices we should simply trust the fact
> that we're receiving an IRK from them to indicate that they may use
> private addresses in the future. Instead, simply tie the persistency
> to the bonding/no-bonding information the same way as for LTKs and
> CSRKs.
> 
> Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx>
> ---
> include/net/bluetooth/hci_core.h |  2 +-
> net/bluetooth/mgmt.c             | 18 ++----------------
> net/bluetooth/smp.c              | 33 +++++++++++++++++----------------
> 3 files changed, 20 insertions(+), 33 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



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux