From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5930ea: shared/gatt-server: Add bt_gatt_server_set_permiss...
Date: Wed, 08 Apr 2026 13:23:50 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1078904/000000-24385d@github.com> (raw)
Branch: refs/heads/1078904
Home: https://github.com/bluez/bluez
Commit: 5930ea25375b48af63d3319da6036ab6e1be9ce5
https://github.com/bluez/bluez/commit/5930ea25375b48af63d3319da6036ab6e1be9ce5
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 Apr 2026)
Changed paths:
M src/shared/gatt-server.c
M src/shared/gatt-server.h
Log Message:
-----------
shared/gatt-server: Add bt_gatt_server_set_permissions
This adds bt_gatt_server_set_permissions which can be used to
enabled/disable permission checking before operations which can be
useful on testing only environment where encryption/pairing is not
desirable/needed.
Commit: 24385dd5330c0c2309bb8082024a2727ee61b29f
https://github.com/bluez/bluez/commit/24385dd5330c0c2309bb8082024a2727ee61b29f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 Apr 2026)
Changed paths:
M src/btd.h
M src/device.c
M src/main.c
M src/main.conf
Log Message:
-----------
main.conf: Add GATT.Security option
This adds GATT.Security option which by default is set to auto to
detect if encryption/authentication is required on demand, but if
Testing is set enables the user to enter a desirable security level.
In case the security level is low it then proceeds to disable checking
GATT attribute permissions for server operations.
Compare: https://github.com/bluez/bluez/compare/5930ea25375b%5E...24385dd5330c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-08 20:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1078904/000000-24385d@github.com \
--to=noreply@github.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox