]> Pileus Git - ~andy/linux/commit
Bluetooth: Default to no security with L2CAP RAW sockets
authorJohan Hedberg <johan.hedberg@intel.com>
Mon, 6 Jan 2014 16:27:02 +0000 (18:27 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Mon, 6 Jan 2014 17:26:23 +0000 (09:26 -0800)
commitcb6ca8e1ed922082bacc6e5e5ee040491a443ea2
treec8f540aef3f91e1d36f5e75dfbcbf3cd79f2ff36
parent8cef8f50d47169b122d7e2dc51fd4370fadd6bfa
Bluetooth: Default to no security with L2CAP RAW sockets

L2CAP RAW sockets can be used for things which do not involve
establishing actual connection oriented L2CAP channels. One example of
such usage is the l2ping tool. The default security level for L2CAP
sockets is LOW, which implies that for SSP based connection
authentication is still requested (although with no MITM requirement),
which is not what we want (or need) for things like l2ping. Therefore,
default to one lower level, i.e. BT_SECURITY_SDP, for L2CAP RAW sockets
in order not to trigger unwanted authentication requests.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap_sock.c