Help understanding Agent 'capabilities'.

[NeilBrown <neilb@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]


Hi,
 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.
 So they seem to be assuming at least one device has a keyboard (the first
 could generate a number in the agent and display it I guess).

 Is there something else I have to change to force it to use Numeric
 comparison (or even 'just works') authentication?  Is this documented
 somewhere?

 I'm using 4.88 on one system and 4.96 on the other.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]