Re: [RFC] LE: Low Latency GATT Write-Sign-Cmd

Hi Johan,

On 22:12 Fri 18 Nov, Johan Hedberg wrote:

Hi Brian,

On Fri, Nov 18, 2011, Brian Gix wrote:

quoted

I would support migrating ATT to the kernel.

Same here.

quoted

In fact another issue I have dealt with is ensuring during Pairing,
that we are able to at least respond with minimal Error responses if
someone tries to read our name, and there is no GATT client socket to
user space to respond.

This issue was already encountered during the last UPF and INdT has a
fix for it. For whatever reason that fix doesn't seem to have showed up
here on the mailing list for upstreaming. 

For that to work, and have a matching userspace and kernel, it needs proper 
support for pairing, i.e. "re-using" a LE link that was used for SMP for 
GATT requests. Those patches are being tested right now, they should
appear on the list soon.

In general the capability of
doing ATT signaling should be available as soon as we have a connection
handle, and it should be independent of any ongoing SMP procedure. Only
if the characteristic accessed requires higher security than is
currently provided by the LE link should the ATT procedures fail with an
error. In the use case you describe, since the Name characteristic
doesn't have any special security requirements a request for it should
be always responded to with a positive reply regardless of the current
level of security or if there's an ongoing SMP operation.

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

Cheers,
-- 
Vinicius