All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@codecoup.pl>
To: linux-bluetooth@vger.kernel.org
Subject: [RFC 0/2] Add support for prepare writes authorization
Date: Wed,  2 May 2018 11:17:55 +0200	[thread overview]
Message-ID: <20180502091757.24190-1-grzegorz.kolodziejczyk@codecoup.pl> (raw)

This patch set adds support for prepare writes authorization handling.
This case covers "GATT/SR/GAW/BI-11-C [Write Long Characteristic Value –
Insufficient Authorization]" PTS test case. If authorization property doesn't
exist or is set to true then daemon doesn't bother application database
with authorization ask and behaves as before.

This patch set is on top of: 72c0c310fd2940d0989af2371728e743894ffcbc
(client: Define maximum attribute value length as initial value)

Grzegorz Kolodziejczyk (2):
  shared/gatt-server: Request authorization for prepare writes.
  client: Add authorized property handling to characteristic attribute

 client/gatt.c            | 46 ++++++++++++++++++++++++++++++++++
 doc/gatt-api.txt         |  8 ++++++
 src/gatt-database.c      |  6 +++++
 src/shared/gatt-server.c | 64 +++++++++++++++++++++++++++++++++++++++++-------
 4 files changed, 115 insertions(+), 9 deletions(-)

-- 
2.13.6


             reply	other threads:[~2018-05-02  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  9:17 Grzegorz Kolodziejczyk [this message]
2018-05-02  9:17 ` [RFC 1/2] shared/gatt-server: Request authorization for prepare writes Grzegorz Kolodziejczyk
2018-05-02 11:32   ` Luiz Augusto von Dentz
2018-05-02 13:31     ` Grzegorz Kołodziejczyk
2018-05-03  9:54       ` Luiz Augusto von Dentz
2018-05-02  9:17 ` [RFC 2/2] client: Add authorized property handling to characteristic attribute Grzegorz Kolodziejczyk
2018-05-02 10:42   ` Luiz Augusto von Dentz
2018-05-02 13:06     ` Grzegorz Kołodziejczyk
2018-05-03  9:58       ` Luiz Augusto von Dentz
2018-05-04 14:03         ` Grzegorz Kołodziejczyk

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=20180502091757.24190-1-grzegorz.kolodziejczyk@codecoup.pl \
    --to=grzegorz.kolodziejczyk@codecoup.pl \
    --cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.