Re: [PATCH] Initial draft of Application registration API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

It should be a RFC instead of PATCH in the subject prefix.

On Fri, Dec 10, 2010 at 1:13 AM, Claudio Takahasi
<claudio.takahasi@xxxxxxxxxxxxx> wrote:
> Add new methods to allow automatic connection when a known remote device
> which supports the wanted services is found.
>
> Overview: RegisterApplication method allows a given application to
> controls the connection establishment procedure for bonded devices.
> StartDiscovery() implements an interleaved discovery, switching between
> inquiry and LE active scanning. For single mode devices found, an
> application can call CreateDevice or CreatePairedDevice, these methods
> will trigger the Discover All Primary Services and SSP(if applied).

Please read SMP instead of SSP for CreatePairedDevice. GATT/ATT
implements a per attribute permission, for BlueZ we are planning to
use CreatePairedDevice to trigger the SMP/key distribution. SMP
negotiation is being implemented completely in the kernel, but at the
moment there isn't key storage and management interface between the
kernel and the userspace to notify the keys. SMP just works method
will be triggered when the client access the first attribute which
requires encryption or when a encrypted link is created.

IMHO, automatic connections needs to be restricted to bonded devices.
If necessary, we can also use the Trusted property.

Claudio
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux