Bluetooth: Fix OOB data present for BR/EDR Secure Connections Only mode
authorMarcel Holtmann <marcel@holtmann.org>
Sat, 31 Jan 2015 21:20:27 +0000 (13:20 -0800)
committerJohan Hedberg <johan.hedberg@intel.com>
Sun, 1 Feb 2015 09:52:54 +0000 (11:52 +0200)
commitbf21d7931a5d33ef79b805074e3d23d3009bff98
treece8a69114bec8fc9544c4797229d0ad4b3419eee
parent6858bcd073c9ff36f5d341dc6da011a53954fa9a
Bluetooth: Fix OOB data present for BR/EDR Secure Connections Only mode

When using Secure Connections Only mode, then only P-256 OOB data is
valid and should be provided. In case userspace provides P-192 and P-256
OOB data, then the P-192 values will be set to zero. However the present
value of the IO capability exchange still mentioned that both values
would be available. Fix this by telling the controller clearly that only
the P-256 OOB data is present.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
net/bluetooth/hci_event.c
This page took 0.024649 seconds and 5 git commands to generate.