Home
last modified time | relevance | path

Searched refs:bond (Results 1 – 15 of 15) sorted by relevance

/Zephyr-Core-3.5.0/tests/bsim/bluetooth/host/gatt/settings/src/
Dutils.h66 void bond(struct bt_conn *conn);
Dserver.c35 bond(conn); in server_round_0()
Dutils.c177 void bond(struct bt_conn *conn) in bond() function
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/shell/
Dcsip.rst22 necessary to bond with the set members. If you need to bond with multiple
/Zephyr-Core-3.5.0/subsys/bluetooth/host/
DKconfig420 forever resolve addresses from that IRK, even if that bond has been
432 bond. However, this naturally limits advertisements from that identity
524 peer where an unauthenticated bond already exists.
527 to replace the existing bond. When this option is disabled in order
528 to create a new bond the old bond has to be explicitly deleted with
532 bool "Delete bond with same peer with other local identity when bonding"
534 When a bond is about to complete, find any other bond with the same
535 peer address (or IRK) and `bt_unpair` that bond before the event
556 bond database and the Controller Resolve List. The implementation
573 peer where an unauthenticated bond already exists on other local
Dssp.c217 bool bond = !atomic_test_bit(conn->flags, BT_CONN_BR_NOBOND); in ssp_pairing_complete() local
223 listener->pairing_complete(conn, bond); in ssp_pairing_complete()
/Zephyr-Core-3.5.0/doc/security/
Dvulnerabilities.rst965 Bluetooth: Possible to overwrite an existing bond during keys
966 distribution phase when the identity address of the bond is known
969 check for an existing bond with the same identity address.This means
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-1.13.rst699 * :github:`3221` - re-pairing with no-bond legacy pairing results in using all zeros LTK
Drelease-notes-2.2.rst39 * :github:`24086` - Bluetooth: SMP: Existing bond deleted on pairing failure
Drelease-notes-2.3.rst1050 * :github:`24086` - Bluetooth: SMP: Existing bond deleted on pairing failure
Drelease-notes-2.0.rst1233 * :github:`15570` - Unbonded peripheral gets 'Tx Buffer Overflow' when erasing bond on master
Drelease-notes-2.5.rst1918 * :github:`15570` - Unbonded peripheral gets 'Tx Buffer Overflow' when erasing bond on master
Drelease-notes-2.7.rst1711 * :github:`35999` - Unexpected Bluetooth disconnection and removal of bond
Drelease-notes-2.6.rst248 * Fixed a bonding issue where the local bond data was not being updated after
Drelease-notes-3.3.rst435 unauthorized bond overrides with multiple identities.