diff options
author | Johan Hedberg <johan.hedberg@intel.com> | 2015-10-12 14:36:19 +0300 |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2015-10-21 01:49:21 +0300 |
commit | cad20c278085d893ebd616cd20c0747a8e9d53c7 (patch) | |
tree | 04bde6709e83fd472e0da063ab08a8d9f52cd936 /block | |
parent | 581d6fd60f37be587690655de05aee200b939e06 (diff) | |
download | linux-cad20c278085d893ebd616cd20c0747a8e9d53c7.tar.xz |
Bluetooth: Don't use remote address type to decide IRK persistency
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@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions