From: "Grzegorz Kołodziejczyk" <grzegorz.kolodziejczyk@codecoup.pl>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 3/5] doc/gatt-api: Add authorization options for attributes
Date: Tue, 22 May 2018 09:33:23 +0200 [thread overview]
Message-ID: <CALevQMbBpXQ351j0u2=iSUMidkpPxnBaBHGNXZxfmaoJzyDBJg@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZ+5jm-PM=bxsCzROaAR2MED9+NUrxvEsynbKb62jPZ-+w@mail.gmail.com>
Hi Luiz,
pon., 21 maj 2018 o 11:44 Luiz Augusto von Dentz <luiz.dentz@gmail.com>
napisa=C5=82(a):
> Hi Grzegorz,
> On Wed, May 16, 2018 at 4:55 PM, Grzegorz Kolodziejczyk
> <grzegorz.kolodziejczyk@codecoup.pl> wrote:
> > This patch adds authorization property for attributes and prepare write
> > request for authorization option for write request. This is require to
> > handle correctly prepare writes, which may response with insufficient
> > authorization error.
> I noticed there also a new error that we should document.
You mean "org.bluez.Error.NotAuthorized" for WriteValue ? If so, it's
already documented as possible error for WriteValues.
> > ---
> > doc/gatt-api.txt | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
> > index 0f1cc9029..7d8c427cd 100644
> > --- a/doc/gatt-api.txt
> > +++ b/doc/gatt-api.txt
> > @@ -85,6 +85,8 @@ Methods array{byte} ReadValue(dict
options)
> > Possible options: "offset": Start offset
> > "device": Device path (Server
only)
> > "link": Link type (Server
only)
> > + "authorize": boolean Is
authorization
> > + request
> >
> > Possible Errors: org.bluez.Error.Failed
> > org.bluez.Error.InProgress
> > @@ -251,6 +253,12 @@ Properties string UUID [read-only]
> > "secure-read" (Server only)
> > "secure-write" (Server only)
> >
> > + boolean Authorize [read-only, optional] (Server only)
> > +
> > + True, if authorization is required for attribut=
e
> > + operations. By default this valuie is set to
false for
> > + attribute.
> > +
> > Characteristic Descriptors hierarchy
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > @@ -284,6 +292,8 @@ Methods array{byte} ReadValue(dict
flags)
> > Possible options: "offset": Start offset
> > "device": Device path (Server
only)
> > "link": Link type (Server
only)
> > + "authorize": boolean Is
authorization
> > + request
> >
> > Possible Errors: org.bluez.Error.Failed
> > org.bluez.Error.InProgress
> > --
> > 2.13.6
> >
> > --
> > 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
> --
> Luiz Augusto von Dentz
Grzegorz Ko=C5=82odziejczyk
next prev parent reply other threads:[~2018-05-22 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 13:55 [PATCH BlueZ v2 3/5] doc/gatt-api: Add authorization options for attributes Grzegorz Kolodziejczyk
2018-05-21 9:44 ` Luiz Augusto von Dentz
2018-05-22 7:33 ` Grzegorz Kołodziejczyk [this message]
2018-05-22 8:01 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2018-05-16 13:52 [PATCH BlueZ v2 1/5] client: Add missing duplicated string free Grzegorz Kolodziejczyk
2018-05-16 13:52 ` [PATCH BlueZ v2 3/5] doc/gatt-api: Add authorization options for attributes Grzegorz Kolodziejczyk
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='CALevQMbBpXQ351j0u2=iSUMidkpPxnBaBHGNXZxfmaoJzyDBJg@mail.gmail.com' \
--to=grzegorz.kolodziejczyk@codecoup.pl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).