From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 000431: mgmt: Add Security Level Changed event
Date: Fri, 25 Sep 2026 07:50:06 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1173703/000000-8edb2c@github.com> (raw)
Branch: refs/heads/1173703
Home: https://github.com/bluez/bluez
Commit: 000431b77b760745d49b5cce73c92f00aeb7da28
https://github.com/bluez/bluez/commit/000431b77b760745d49b5cce73c92f00aeb7da28
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M doc/mgmt-protocol.rst
M lib/bluetooth/mgmt.h
Log Message:
-----------
mgmt: Add Security Level Changed event
This provides a TLV list of values related to the security level of
the connection to a remote device.
Currently Security Level and Encryption type are implemented.
Commit: d4be6bb3e2d167d9e48461f986a13e2d7bf872b9
https://github.com/bluez/bluez/commit/d4be6bb3e2d167d9e48461f986a13e2d7bf872b9
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M tools/mgmt-tester.c
Log Message:
-----------
mgmt-tester: Add Security Level Changed event tests
Test that MGMT_EV_SECURITY_LEVEL_CHANGED is correctly received during
BREDR and LE secured connection.
Assisted-by: GPT:GPT-5.3-Codex
Commit: 2650b3cefe65735d0107efcf8fc941480362cde3
https://github.com/bluez/bluez/commit/2650b3cefe65735d0107efcf8fc941480362cde3
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: Add support for Mgmt Security Level changed event
@ MGMT Event: Security Level Changed (0x0034) plen 16
BR/EDR Address: 00:AA:01:01:00:00 (Intel Corporation)
Count: 2
Security Level: No security (0x00000000)
Encryption Type: No encryption (0x00000000)
Commit: da763adc7bdb4fc3c3ea14f7c30afa13ace9b968
https://github.com/bluez/bluez/commit/da763adc7bdb4fc3c3ea14f7c30afa13ace9b968
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
Log Message:
-----------
device: Add SecurityLevel properties to org.bluez.Device1
This uses the new MGMT_EV_SECURITY_LEVEL_CHANGED event.
It will be used by btpclient to reduce test time.
Commit: d84ff3ce7d20ef2e8eb691db3f65259c8fe30366
https://github.com/bluez/bluez/commit/d84ff3ce7d20ef2e8eb691db3f65259c8fe30366
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M doc/org.bluez.Device.rst
Log Message:
-----------
org.bluez.Device: Add Security Level related properties
This adds the SecurityLevel and EncryptionType properties which can be
used by clients to get the security level and encryption type in use
for a connection.
Commit: 8edb2cbb3cd687ac39e7b17e826108fcda6cf376
https://github.com/bluez/bluez/commit/8edb2cbb3cd687ac39e7b17e826108fcda6cf376
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Display SecurityLevel in device info
Compare: https://github.com/bluez/bluez/compare/000431b77b76%5E...8edb2cbb3cd6
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-25 14:50 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/1173703/000000-8edb2c@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