linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Help understanding Agent 'capabilities'.
Date: Thu, 13 Oct 2011 10:48:23 +0300	[thread overview]
Message-ID: <20111013074823.GD8289@fusion.localdomain> (raw)
In-Reply-To: <20111013165526.0dbbe0fc@notabene.brown>

Hi Neil,

On Thu, Oct 13, 2011, NeilBrown wrote:
>  I've been trying enhance my understanding of bluetooth and as part of that
>  I have been experimenting with simple-agent to create pairing between two
>  Linux hosts (a phone and a laptop as it happens).
> 
>  My understanding of Secure Simple Pairing is that there are a number of
>  authentication mechanism and that the "best" would be chosen based on the
>  that capabilities given to the agent.
> 
>  So if both devices tell the monitor "DisplayYesNo", it would not be able to
>  do Passkey entry and would choose Numeric comparison.
>  So both agents would get RequestConfirmation call backs.
> 
>  But I cannot make that happen.
> 
>  No matter what capability I give to simple-agent, one of them asks me for a
>  pass key, then the other one does, and they have to match.  i.e. they both
>  get RequestPinCode.

If you get RequestPinCode it means that at least one of the devices
isn't capable of SSP, i.e. is a pre-2.1 Bluetooth controller. In such
cases the IO capability is irrelevant (as the concept doesn't exist for
2.0 and older devices).

Johan

      parent reply	other threads:[~2011-10-13  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  5:55 Help understanding Agent 'capabilities' NeilBrown
2011-10-13  7:39 ` Luiz Augusto von Dentz
2011-10-13 11:14   ` NeilBrown
2011-10-13 11:28     ` Johan Hedberg
2011-10-16 21:27       ` NeilBrown
2011-10-13  7:48 ` Johan Hedberg [this message]

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=20111013074823.GD8289@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).