Home
last modified time | relevance | path

Searched refs:pairing (Results 1 – 21 of 21) sorted by relevance

/Zephyr-Core-3.4.0/subsys/bluetooth/host/
DKconfig189 (and restoring) the Bluetooth state (e.g. pairing keys) and
365 Passkey Entry during pairing.
456 bool "Accept or reject pairing initiative"
458 When receiving pairing request or pairing response query the
459 application whether to accept to proceed with pairing or not. This is
460 for pairing over SMP and does not affect SSP, which will continue
461 pairing without querying the application.
463 a SMP return value if the pairing is not allowed.
466 bool "Disable legacy pairing"
468 This option disables LE legacy pairing and forces LE secure connection
[all …]
DCMakeLists.txt101 A fixed passkey is easy to deduce during the pairing procedure, do not use in
Dsmp.c2083 static uint8_t smp_pairing_accept_query(struct bt_smp *smp, struct bt_smp_pairing *pairing) in smp_pairing_accept_query() argument
2091 .io_capability = pairing->io_capability, in smp_pairing_accept_query()
2092 .oob_data_flag = pairing->oob_flag, in smp_pairing_accept_query()
2093 .auth_req = pairing->auth_req, in smp_pairing_accept_query()
2094 .max_enc_key_size = pairing->max_key_size, in smp_pairing_accept_query()
2095 .init_key_dist = pairing->init_key_dist, in smp_pairing_accept_query()
2096 .resp_key_dist = pairing->resp_key_dist in smp_pairing_accept_query()
/Zephyr-Core-3.4.0/samples/boards/reel_board/mesh_badge/
DREADME.rst30 #. Press "Send" - this will trigger pairing since this is a protected
31 characteristic. The passkey for the pairing will be shown on the board's
33 #. Once pairing is complete the board will show the text you sent. If
/Zephyr-Core-3.4.0/samples/bluetooth/peripheral_hids/
DREADME.rst15 pairing) and requires an authenticated link to access the GATT characteristics.
/Zephyr-Core-3.4.0/samples/bluetooth/encrypted_advertising/
DREADME.rst46 button on both boards to confirm the pairing request.
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/
Dbluetooth-arch.rst315 called pairing is used. This process can either be triggered implicitly
321 out-of-band channel during the pairing. If the devices have a sufficient
325 a set of optional callbacks that can be used during the pairing - if the
342 Encryption and authentication using the legacy pairing method
351 provisioning. It follows a similar procedure as pairing, but is done
/Zephyr-Core-3.4.0/tests/bsim/
DREADME.md77 pairing, powering off, and powering up after as a new simulation,
/Zephyr-Core-3.4.0/doc/releases/
Drelease-notes-1.6.rst101 * Added cross-transport pairing support for the Security Manager Protocol.
340 * ``ZEP-1221`` - Connection Timeout during pairing
Drelease-notes-2.0.rst420 * Completed support for directed advertising and Out-Of-Band (OOB) pairing
422 forcing a pairing procedure in case of key loss
535 * :github:`18705` - SMP fails to allocate buffer and pairing times out
575 * :github:`18580` - Bluetooth: Security fail on initial pairing
828 …`17525` - L2CAP: On insufficient authentication error received, Zephyr does unauthenticated pairing
931 * :github:`17013` - Bluetooth: Add error reason to pairing failed callbacks
1512 * :github:`2587` - Support for BR/EDR SSP out-of-band pairing
1513 * :github:`2586` - Support for LE SC out-of-band pairing
Drelease-notes-1.13.rst528 * :github:`8390` - bluetooth: request APIs to notify application that pairing is complete or not
543 * :github:`8350` - bluetooth: request BLE stack to support pre-set passkey for pairing
699 * :github:`3221` - re-pairing with no-bond legacy pairing results in using all zeros LTK
Drelease-notes-2.3.rst626 * Legacy OOB pairing support has been added.
627 * Multiple improvements to OOB data access and pairing.
1050 * :github:`24086` - Bluetooth: SMP: Existing bond deleted on pairing failure
1457 * :github:`2585` - Support for LE legacy out-of-band pairing
Drelease-notes-3.4.rst257 * :c:func:`bt_le_oob_set_sc_flag` for setting/clearing OOB flag in SC pairing
422 * Separated the handling of LE SC OOB pairing from the legacy OOB logic.
Drelease-notes-1.14.rst213 * :github:`18580` - Bluetooth: Security fail on initial pairing
421 * :github:`18580` - Bluetooth: Security fail on initial pairing
1609 * :github:`13083` - Problem pairing/bonding 2nd device, whilst the first device is still connected …
1639 * :github:`12946` - Zephyr/BLE stack: Problem pairing/bonding more than one device, whilst the firs…
2054 * :github:`10460` - Bluetooth: settings: No space to store CCC config after successful pairing
Drelease-notes-1.10.rst365 * :github:`4044` - Livelock in SMP pairing failed scenario
Drelease-notes-2.6.rst269 * Changed the pairing procedure to fail pairing when both sides have the same
274 * Fixed an issue where callbacks for "security changed" and "pairing failed"
276 * Changed the pairing procedure to fail early if the remote device could not
Drelease-notes-2.5.rst963 * :github:`31607` - Bluetooth: host: bt_conn_auth_cb callbacks are not called when pairing to BLE 4…
1935 * :github:`10460` - Bluetooth: settings: No space to store CCC config after successful pairing
Drelease-notes-2.7.rst1088 * :github:`38782` - CONFIG_BT_CTLR_DATA_LENGTH_MAX=250 causes pairing compatibility issues with man…
1472 * :github:`37228` - Bluetooth SMP does not complete pairing
Drelease-notes-2.2.rst39 * :github:`24086` - Bluetooth: SMP: Existing bond deleted on pairing failure
Drelease-notes-3.3.rst439 * Modified the SMP behavior when outside a pairing procedure. The stack no
/Zephyr-Core-3.4.0/subsys/bluetooth/shell/
Dbt.c4072 SHELL_CMD_ARG(auth-pairing-confirm, NULL, HELP_NONE,