From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7a55a6: mgmt-tester: Fix LE Security Level Changed expecte...
Date: Fri, 02 Oct 2026 09:43:14 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/ae69dc-4dc15b@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 7a55a67cb49bce2e302963ee0fca627ec3b270c7
https://github.com/bluez/bluez/commit/7a55a67cb49bce2e302963ee0fca627ec3b270c7
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M tools/mgmt-tester.c
Log Message:
-----------
mgmt-tester: Fix LE Security Level Changed expected encryption type
LE pairing results in an AES-CCM encrypted link, so expect
MGMT_CONN_SEC_ENCRYPT_AES_CCM instead of MGMT_CONN_SEC_ENCRYPT_NONE,
which only matched the event emitted on connection before pairing.
Fixes: 74334ac97049 ("mgmt-tester: Add Security Level Changed event tests")
Assisted-by: OpenCode:claude-opus-5.5
Commit: 75a778e17f49560097c684058a9ff814e2279bfc
https://github.com/bluez/bluez/commit/75a778e17f49560097c684058a9ff814e2279bfc
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M doc/org.bluez.Device.rst
Log Message:
-----------
org.bluez.Device: Add Connectable property
This adds Connectable property which indicates whether the remote
device accepts connections, as reported by its last advertising report
or inquiry result.
bluetoothd already tracks this per bearer from the Device Found event,
but it is not exposed over D-Bus, so applications cannot tell
connectable advertisers such as peripherals from non-connectable ones
such as beacons without attempting a connection.
Commit: f890d4b660c664ccca0e146ecfd2d58688f917d7
https://github.com/bluez/bluez/commit/f890d4b660c664ccca0e146ecfd2d58688f917d7
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M doc/org.bluez.Bearer.BREDR.rst
M doc/org.bluez.Bearer.LE.rst
Log Message:
-----------
org.bluez.Bearer: Add Connectable property
This adds Connectable property to org.bluez.Bearer.LE1 and
org.bluez.Bearer.BREDR1, so it is possible to tell which bearer of a
dual-mode device accepts connections, since Device1.Connectable is
always true for them as BREDR is always considered connectable.
Commit: 6afb6e729270a3e85f020c724baae621a413fc8e
https://github.com/bluez/bluez/commit/6afb6e729270a3e85f020c724baae621a413fc8e
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M src/device.c
Log Message:
-----------
device: Add Connectable property
This implements Connectable property using device_is_connectable, which
reports whether the last advertising report on the device's bearer was
connectable, and emits PropertiesChanged from device_update_last_seen
when the value changes or first becomes known.
Commit: ab50d5e88fb652f1a1c35336c1aab632b2e80993
https://github.com/bluez/bluez/commit/ab50d5e88fb652f1a1c35336c1aab632b2e80993
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M src/bearer.c
M src/bearer.h
M src/device.c
M src/device.h
Log Message:
-----------
bearer: Add Connectable property
This implements Connectable property for both bearers. For LE it
reflects whether the last advertising report was connectable, and
PropertiesChanged is emitted from device_update_last_seen when it
changes or first becomes known. BREDR always reports it as true.
Commit: 82f671c83429aa3548a26c92e05d3e7125356068
https://github.com/bluez/bluez/commit/82f671c83429aa3548a26c92e05d3e7125356068
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Print Connectable in info
This prints the Connectable property of the device and its bearers with
the likes of info command:
bluetoothctl> info <addr>
...
Connectable: yes
...
LE.Connectable: yes
Commit: 4dc15be8ee3f7422d447087f1893d215575cb2c8
https://github.com/bluez/bluez/commit/4dc15be8ee3f7422d447087f1893d215575cb2c8
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Print discoverable broadcasters in red
This prints devices in red when they set the discoverable flags but are
not connectable, to warn the user they cannot be connected to despite
being discoverable.
Compare: https://github.com/bluez/bluez/compare/ae69dcddd549...4dc15be8ee3f
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-02 16:43 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/master/ae69dc-4dc15b@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