summaryrefslogtreecommitdiff
path: root/tools/l2cap-tester.c
diff options
context:
space:
mode:
authorAnderson Lizardo <anderson.lizardo@openbossa.org>2014-01-24 21:54:01 -0400
committerJohan Hedberg <johan.hedberg@intel.com>2014-01-26 00:09:41 +0200
commite34d1c0481e1619c0cb92b89e50203c56f479a0f (patch)
tree194e5749bd7049feb271223ad3c0c1d034419b53 /tools/l2cap-tester.c
parentccbbb8dd3ce840b332b4d5b971bd58609396a043 (diff)
downloadbluez-e34d1c0481e1619c0cb92b89e50203c56f479a0f.tar.gz
tools/l2cap-tester: Test setsockopt(BT_SECURITY) on LE client
Although setting a security level using setsockopt(BT_SECURITY) is optional for LE sockets (it will default to doing unencrypted/unauthenticated connection), it is a common operation and it is done by BlueZ daemon and some tools.
Diffstat (limited to 'tools/l2cap-tester.c')
-rw-r--r--tools/l2cap-tester.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/l2cap-tester.c b/tools/l2cap-tester.c
index 05202bd96..d541f1b7e 100644
--- a/tools/l2cap-tester.c
+++ b/tools/l2cap-tester.c
@@ -461,6 +461,7 @@ static const struct l2cap_data le_server_success_test = {
static const struct l2cap_data le_att_client_connect_success_test_1 = {
.cid = 0x0004,
+ .sec_level = BT_SECURITY_LOW,
};
static const struct l2cap_data le_att_server_success_test_1 = {