linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tony <tony.makkiel@convergeddevices.net>
To: <linux-bluetooth@vger.kernel.org>
Subject: SEC SEM BV 09, MITM + No Bonding
Date: Wed, 19 Aug 2015 14:23:26 +0100	[thread overview]
Message-ID: <55D4834E.9080705@convergeddevices.net> (raw)

Hi All,
            I am going through Bluez 4.101 qualification process and am 
stuck with second part of test case SEC SEM BV 09. The test case needs 
BlueZ to connect to Tester with Authentication requirement 0 (MITM not 
required + No Bonding). Then have to trigger another L2CAP connection 
with Authentication requirement 1 (MITM required + No Bonding).

We managed to get through the first part using l2test
l2test -n -P 1 -E
But the second part always does general bonding (Authentication 
Requirement 5).
l2test -n -S -P 17 -J 2

Can somebody please advise on how to force blueZ to initiate connection 
with authentication requirement 1 (MITM required + No Bonding)? From the 
blueZ code, I noticed it follows lead from the remote device. But 
couldn't find anything obvious when initiating connection.

Many Thanks,
Tony

             reply	other threads:[~2015-08-19 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 13:23 tony [this message]
2015-08-19 16:23 ` SEC SEM BV 09, MITM + No Bonding Johan Hedberg
2015-08-28 14:44   ` tony
2015-09-02 14:50   ` Bluez-4.101 LE SMP support tony
2015-09-02 17:09     ` Marcel Holtmann
     [not found]     ` <563A1880.8000608@convergeddevices.net>
2015-11-05  9:12       ` BlueZ-5.36 segfault Luiz Augusto von Dentz
2015-11-05 10:40         ` tony

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55D4834E.9080705@convergeddevices.net \
    --to=tony.makkiel@convergeddevices.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).