Johan Hedberg 88644bb9fe Revert "Bluetooth: Update sec_level/auth_type for already existing connections" ... This reverts commit 045309820a. That commit is wrong for two reasons: - The conn->sec_level shouldn't be updated without performing authentication first (as it's supposed to represent the level of security that the existing connection has) - A higher auth_type value doesn't mean "more secure" like the commit seems to assume. E.g. dedicated bonding with MITM protection is 0x03 whereas general bonding without MITM protection is 0x04. hci_conn_auth already takes care of updating conn->auth_type so hci_connect doesn't need to do it. Signed-off-by: Johan Hedberg <johan.hedberg@nokia.com> Acked-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>		2011-01-19 14:40:42 -02:00
..
bnep
cmtp
hidp
rfcomm	Bluetooth: Never deallocate a session when some DLC points to it	2011-01-19 14:40:42 -02:00
af_bluetooth.c
hci_conn.c	Revert "Bluetooth: Update sec_level/auth_type for already existing connections"	2011-01-19 14:40:42 -02:00
hci_core.c	Bluetooth: Fix leaking blacklist when unregistering a hci device	2011-01-19 14:40:42 -02:00
hci_event.c	Bluetooth: Fix __hci_request synchronization for hci_open_dev	2010-12-22 22:58:07 -02:00
hci_sock.c	Bluetooth: Improve handling of HCI control channel in bind	2010-12-22 23:00:34 -02:00
hci_sysfs.c
Kconfig
l2cap.c	Bluetooth: l2cap: fix misuse of logical operation in place of bitop	2011-01-19 14:40:42 -02:00
lib.c
Makefile
mgmt.c	Bluetooth: Add management events for controller addition & removal	2010-12-22 22:58:00 -02:00
sco.c