All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dagan Martinez <martinez.dagan@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Dagan Martinez <martinez.dagan@gmail.com>
Subject: [PATCH BlueZ 0/1] gatt: remove superfluous extended properties
Date: Sun, 26 Sep 2021 13:00:38 -0400	[thread overview]
Message-ID: <20210926170039.49865-1-martinez.dagan@gmail.com> (raw)

As discussed on Slack, the BlueZ source contains superfluous
non-standard extended properties with no effect other than the creation
of unnecessary CEPDs with bits set in the "reserved" field. These
extended properties are set when a characteristic has a `secure-*`,
`encrypt-*`, or `encrypt-authenticated-*` flag set.

According to section 3.3.3.1 of the Bluetooth core spec 5.3, the only
valid extended properties are "reliable write", and "writable
auxiliaries."

This patch removes all other extended properties.

Dagan Martinez (1):
  gatt: remove superfluous extended properties

 src/gatt-database.c    | 6 ------
 src/shared/att-types.h | 8 --------
 2 files changed, 14 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-09-26 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 17:00 Dagan Martinez [this message]
2021-09-26 17:00 ` [PATCH BlueZ 1/1] gatt: remove superfluous extended properties Dagan Martinez
2021-09-26 17:38   ` bluez.test.bot
2021-09-27 17:45     ` Luiz Augusto von Dentz

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=20210926170039.49865-1-martinez.dagan@gmail.com \
    --to=martinez.dagan@gmail.com \
    --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.