linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Brian Gix <bgix@codeaurora.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] LE: Low Latency GATT Write-Sign-Cmd
Date: Fri, 18 Nov 2011 22:12:13 +0200	[thread overview]
Message-ID: <20111118201213.GA22216@x220.ger.corp.intel.com> (raw)
In-Reply-To: <4EC6B8F0.2040904@codeaurora.org>

Hi Brian,

On Fri, Nov 18, 2011, Brian Gix wrote:
> I would support migrating ATT to the kernel.

Same here.

> 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. 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

  reply	other threads:[~2011-11-18 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 18:17 [RFC] LE: Low Latency GATT Write-Sign-Cmd Brian Gix
2011-11-18 19:08 ` Marcel Holtmann
2011-11-18 19:58   ` Brian Gix
2011-11-18 20:12     ` Johan Hedberg [this message]
2011-11-18 20:19       ` Brian Gix
2011-11-18 23:50       ` Vinicius Costa Gomes
2011-11-18 20:36   ` Anderson Lizardo
2011-11-18 20:48     ` Brian Gix
2011-11-18 20:58       ` Anderson Lizardo
2011-11-18 21:16         ` Brian Gix

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=20111118201213.GA22216@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=bgix@codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).