Bluetooth: Fix authentication requirements for L2CAP security check
authorMarcel Holtmann <marcel@holtmann.org>
Thu, 12 Feb 2009 15:19:45 +0000 (16:19 +0100)
committerMarcel Holtmann <marcel@holtmann.org>
Fri, 27 Feb 2009 05:14:43 +0000 (06:14 +0100)
commit00ae4af91d8c5b6814e2bb3bfaaf743845f989eb
tree616da6330e5b9ca7448234fbd588c536da165d11
parent2950f21acb0f6b8fcd964485c2ebf1e06545ac20
Bluetooth: Fix authentication requirements for L2CAP security check

The L2CAP layer can trigger the authentication via an ACL connection or
later on to increase the security level. When increasing the security
level it didn't use the same authentication requirements when triggering
a new ACL connection. Make sure that exactly the same authentication
requirements are used. The only exception here are the L2CAP raw sockets
which are only used for dedicated bonding.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap.c