Branch: refs/heads/master Home: https://github.com/bluez/bluez Commit: bbc1c2a7f06e3a77af70e1e030df047afe6a6d3a https://github.com/bluez/bluez/commit/bbc1c2a7f06e3a77af70e1e030df047afe6a6d3a Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-03-26 (Wed, 26 Mar 2025) Changed paths: M src/main.c Log Message: ----------- main: Fix handling of legacy experimental LL Privacy Legacy experimental LL Privacy was not enabled by default but CentralAddressResolution is which may cause problems with old kernels were LL Privacy may not work as expected. Fixes: https://github.com/bluez/bluez/issues/1138 Commit: 8e2cece67dbe2bc92900a8fb72fed19fe114ea3e https://github.com/bluez/bluez/commit/8e2cece67dbe2bc92900a8fb72fed19fe114ea3e Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-03-26 (Wed, 26 Mar 2025) Changed paths: M src/device.c Log Message: ----------- device: Attempt to elevate security on Pair while connected This would make Pair act behave the same as when the device reconnect and bonding already exists. Commit: 1c2ec29900e48c785f7faa8fbe88f3085aaf806b https://github.com/bluez/bluez/commit/1c2ec29900e48c785f7faa8fbe88f3085aaf806b Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-03-26 (Wed, 26 Mar 2025) Changed paths: M src/device.c Log Message: ----------- device: Make Connect and Pair mutually exclusive This makes Device.Connect and Device.Pair methods mutually exclusive so they cannot happen in parallel, so just as Connect:Connect and Pair:Pair combinations the Connect:Pair and Pair:Connect will now return org.bluez.Error.InProgress. Commit: 45b61a10bd0af9b0b13f508166369eb1138ae448 https://github.com/bluez/bluez/commit/45b61a10bd0af9b0b13f508166369eb1138ae448 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-03-26 (Wed, 26 Mar 2025) Changed paths: M src/device.c Log Message: ----------- device: Use btd_device_is_initiator instead of Connect message Device.Connect message is not the only way to initiate a connection as there is also the likes of Device.Pair which will initiate bonding, so this incorporate the bonding check into btd_device_is_initiator and replaces the checks of were Connect message was used to determine if initiator to use btd_device_is_initiator. Commit: ac1f8dd88a46da193b9226724a3ac60a0876598a https://github.com/bluez/bluez/commit/ac1f8dd88a46da193b9226724a3ac60a0876598a Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-03-26 (Wed, 26 Mar 2025) Changed paths: M src/shared/att.c Log Message: ----------- shared/att: Make bt_att_set_security never downgrade security level Requesting a lower security level than existing one shall result in no operation since higher security satisfy a lower one and it is never a good practice to allow downgrading security to begin with. Commit: 5df9521ce4d50ffa48153503bc5156c11e6ed26b https://github.com/bluez/bluez/commit/5df9521ce4d50ffa48153503bc5156c11e6ed26b Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-03-26 (Wed, 26 Mar 2025) Changed paths: M src/device.c Log Message: ----------- device: Elevate bt_att security if bonding is in progress When bonding is in progress it means Device.Pair has been called thus the user indicated the intend to pair/bond from the start so the security of bt_att shall be set in order for it to wait until pairing process complete before attempting to proceed with GATT discovery and any other traffic. Fixes: https://github.com/bluez/bluez/issues/1125 Compare: https://github.com/bluez/bluez/compare/0f0039045088...5df9521ce4d5 To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
