From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] faca31: shared/bass: Fix permissions not requiring encryption
Date: Thu, 02 Oct 2025 09:36:27 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/73dd85-3e5547@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: faca31657e1b0cec0e03bbb7bf0e2d81222079d4
https://github.com/bluez/bluez/commit/faca31657e1b0cec0e03bbb7bf0e2d81222079d4
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-10-02 (Thu, 02 Oct 2025)
Changed paths:
M src/shared/bass.c
M unit/test-bass.c
Log Message:
-----------
shared/bass: Fix permissions not requiring encryption
Both Broadcast Audio Scan Control Point and Broadcast Receive State do
require encryption:
https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/24670-BASS-html5/out/en/index-en.html#UUID-dd95da9a-6ac0-3f45-7e34-13fa9e04d41c
Commit: 3e55476bf6c8ed4180d6cc70ff7cde524e6f1bfa
https://github.com/bluez/bluez/commit/3e55476bf6c8ed4180d6cc70ff7cde524e6f1bfa
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-10-02 (Thu, 02 Oct 2025)
Changed paths:
M client/player.c
Log Message:
-----------
client/player: Set QoS.Encryption if QoS.BCode is set
QoS.Encryption must be set in order for the daemon to interpret the
QoS.BCode as valid.
Compare: https://github.com/bluez/bluez/compare/73dd85a18b13...3e55476bf6c8
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-02 16:36 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/73dd85-3e5547@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