tree 04bde6709e83fd472e0da063ab08a8d9f52cd936
parent 581d6fd60f37be587690655de05aee200b939e06
author Johan Hedberg <johan.hedberg@intel.com> 1444649779 +0200
committer Marcel Holtmann <marcel@holtmann.org> 1445381361 +0200

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>