You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Marcel Holtmann 3fdca1e137 Bluetooth: Fix connection establishment with low security requirement ... The Bluetooth 2.1 specification introduced four different security modes that can be mapped using Legacy Pairing and Simple Pairing. With the usage of Simple Pairing it is required that all connections (except the ones for SDP) are encrypted. So even the low security requirement mandates an encrypted connection when using Simple Pairing. When using Legacy Pairing (for Bluetooth 2.0 devices and older) this is not required since it causes interoperability issues. To support this properly the low security requirement translates into different host controller transactions depending if Simple Pairing is supported or not. However in case of Simple Pairing the command to switch on encryption after a successful authentication is not triggered for the low security mode. This patch fixes this and actually makes the logic to differentiate between Simple Pairing and Legacy Pairing a lot simpler. Based on a report by Ville Tervo <ville.tervo@nokia.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>		16 years ago
..
bnep	…
cmtp	…
hidp	…
rfcomm	…
Kconfig	…
Makefile	…
af_bluetooth.c	…
hci_conn.c	Bluetooth: Fix connection establishment with low security requirement	16 years ago
hci_core.c	…
hci_event.c	Bluetooth: Add different pairing timeout for Legacy Pairing	16 years ago
hci_sock.c	…
hci_sysfs.c	Bluetooth: Ensure that HCI sysfs add/del is preempt safe	16 years ago
l2cap.c	…
lib.c	…
sco.c	…