* [bluez/bluez] 00969b: device: Reply br-connection-key-missing on connect...
@ 2025-05-15 20:15 fdanis-oss
0 siblings, 0 replies; only message in thread
From: fdanis-oss @ 2025-05-15 20:15 UTC (permalink / raw)
To: linux-bluetooth
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 00969bdb17ea01af8722d5bdcf8b2c19e06e9456
https://github.com/bluez/bluez/commit/00969bdb17ea01af8722d5bdcf8b2c19e06e9456
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-05-15 (Thu, 15 May 2025)
Changed paths:
M src/device.c
Log Message:
-----------
device: Reply br-connection-key-missing on connection bonding error
Currently when connection is removed while the client is waiting for
Connect() the failed message is br-connection-canceled, even if this
is due to bonding error.
Implement to reply with br-connection-key-missing, when the connection
request fails due to a bonding authentication error, allowing the client
to differentiate connection failure reasons.
This has been tested by:
- pair a device
- disconnect
- edit pairing info to change last character of Key entry of [LinkKey] in
/var/lib/bluetooth/<adapter_address>/<device_address>?info
- restart bluetoothd
- in bluetoothctl, connect <device_address>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-05-15 20:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-15 20:15 [bluez/bluez] 00969b: device: Reply br-connection-key-missing on connect fdanis-oss
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.