Marcel Holtmann 53ac6ab612 Bluetooth: Make LTK and CSRK only persisent when bonding ... In case the pairable option has been disabled, the pairing procedure does not create keys for bonding. This means that these generated keys should not be stored persistently. For LTK and CSRK this is important to tell userspace to not store these new keys. They will be available for the lifetime of the device, but after the next power cycle they should not be used anymore. Inform userspace to actually store the keys persistently only if both sides request bonding. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>		2014-03-10 14:57:33 +02:00
..
bluetooth.h	Bluetooth: Introduce requirements for security level 4	2014-02-13 09:51:35 +02:00
hci_core.h	Bluetooth: Make LTK and CSRK only persisent when bonding	2014-03-10 14:57:33 +02:00
hci_mon.h	Bluetooth: Fix coding style in all .h files	2012-03-07 00:04:25 -03:00
hci.h	Bluetooth: Remove unnecessary stop_scan_complete function	2014-02-28 10:28:17 -08:00
l2cap.h	Bluetooth: Fix updating Identity Address in L2CAP channels	2014-02-18 11:48:55 -08:00
mgmt.h	Bluetooth: Add support for handling signature resolving keys	2014-03-09 21:39:50 +02:00
rfcomm.h	Bluetooth: Don't fail RFCOMM tty writes	2014-02-14 13:39:32 -08:00
sco.h	Bluetooth: Store SCO address information in its own socket structure	2013-10-13 21:11:20 +03:00