device: Fix resolving a coordinated set over Secure Connections
Status from this message: This series was applied to bluetooth/bluez.git (master)
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | mgmt: Add defines for the long term key typeslib/ | +6 | 1 reply | |
| 2/4 | device: Remove unused central field from struct ltk_infoprofiles/ src/ src/ | +3 | 0 replies | |
| 3/4 | device: Fix resolving a coordinated set over Secure Connectionssrc/ src/ src/ | +31 | 0 replies | |
| 4/4 | test: functional: run CSIP test for Secure Connections & Legacy Pairingtest/ | +18 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH BlueZ 0/4] device: Fix resolving a coordinated set over Secure Connections
CSIP coordinator was not finding its LTKs with Secure Connections, as the fix in 9251e630efdd to make legacy pairing to work doesn't work with SC.
Fix by keeping track of what kind of LTK we have, and not distinguishing between central/peripheral key slots for SC, which kernel doesn't do and AFAIK the role difference doesn't exist in SC.
LLM was used for bug triage and write initial version, but these are now almost manually done.
Pauli Virtanen (4):
mgmt: Add defines for the long term key types
device: Remove unused central field from struct ltk_info
device: Fix resolving a coordinated set over Secure Connections
test: functional: run CSIP test for Secure Connections & Legacy
Pairing
lib/bluetooth/mgmt.h | 6 ++++++ profiles/audio/csip.c | 2 +- src/adapter.c | 5 +++-- src/device.c | 39 ++++++++++++++++++++++++++----------- src/device.h | 4 ++-- test/functional/test_bap.py | 21 +++++++++++++++++--- 6 files changed, 58 insertions(+), 19 deletions(-)
Signature · 1 line
2.55.0