linux/include/net/bluetooth
Marcel Holtmann 435fef20ac Bluetooth: Don't enforce authentication for L2CAP PSM 1 and 3
The recommendation for the L2CAP PSM 1 (SDP) is to not use any kind
of authentication or encryption. So don't trigger authentication
for incoming and outgoing SDP connections.

For L2CAP PSM 3 (RFCOMM) there is no clear requirement, but with
Bluetooth 2.1 the initiator is required to enable authentication
and encryption first and this gets enforced. So there is no need
to trigger an additional authentication step. The RFCOMM service
security will make sure that a secure enough link key is present.

When the encryption gets enabled after the SDP connection setup,
then switch the security level from SDP to low security.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
2009-02-27 06:14:41 +01:00
..
bluetooth.h Bluetooth: Add enhanced security model for Simple Pairing 2009-02-27 06:14:25 +01:00
hci_core.h Bluetooth: Don't enforce authentication for L2CAP PSM 1 and 3 2009-02-27 06:14:41 +01:00
hci.h Bluetooth: Add SCO fallback for eSCO connection attempts 2009-02-27 06:14:37 +01:00
l2cap.h Bluetooth: Fix double L2CAP connection request 2009-02-27 06:14:41 +01:00
rfcomm.h Bluetooth: Pause RFCOMM TX when encryption drops 2009-02-27 06:14:33 +01:00
sco.h Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00