summaryrefslogtreecommitdiff
path: root/net/bluetooth/rfcomm
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2008-07-14 18:13:54 (GMT)
committerMarcel Holtmann <marcel@holtmann.org>2008-07-14 18:13:54 (GMT)
commitb1235d79611e78a07629b4cbe53291c9cffd1834 (patch)
treeb12b694d991e62a761d48ee4bb12b6eade753f78 /net/bluetooth/rfcomm
parent7cb127d5b0e7af7a0afd23785722ca3edab4ceff (diff)
downloadlinux-b1235d79611e78a07629b4cbe53291c9cffd1834.tar.xz
[Bluetooth] Allow security for outgoing L2CAP connections
When requested the L2CAP layer will now enforce authentication and encryption on outgoing connections. The usefulness of this feature is kinda limited since it will not allow proper connection ownership tracking until the authentication procedure has been finished. This is a limitation of Bluetooth 2.0 and before and can only be fixed by using Simple Pairing. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/rfcomm')
0 files changed, 0 insertions, 0 deletions