Bluetooth: Don't use non-resolvable private address for passive scanning
authorMarcel Holtmann <marcel@holtmann.org>
Sun, 29 Jun 2014 10:20:15 +0000 (12:20 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 3 Jul 2014 15:42:49 +0000 (17:42 +0200)
commit6ab535a777d76a2b1e5ad03119cd0c1e5a366b06
tree15c684de6e81a9e2d1cb35bfa870f0e27313d66e
parentfee746b0babf128a50ece050ee6e63003ebb5ae1
Bluetooth: Don't use non-resolvable private address for passive scanning

The usage of non-resovlable private addresses for passive scanning is
a bad idea. Passive scanning will not send any SCAN_REQ and thus using
your identity address for passive scanning is not a privacy issue.

It is important to use the identity address during passive scanning
since that is the only way devices using direct advertising will be
reported correctly by the controller. This is overlooked detail in
the Bluetooth specification that current controllers are not able
to report direct advertising events for other than their current
address.

When remote peers are using direct advertising and scanning is done
with non-resolvable private address these devices will not be found.

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