Home
last modified time | relevance | path

Searched refs:privacy (Results 1 – 25 of 26) sorted by relevance

12

/Zephyr-Core-3.4.0/tests/bsim/bluetooth/host/privacy/device/
DREADME.rst9 The tests check the following aspects of the Bluetooth privacy feature:
11 * In device privacy mode, a scanner shall accept advertising packets from peers with any address
/Zephyr-Core-3.4.0/tests/bsim/bluetooth/host/
Dcompile.sh59 app=tests/bsim/bluetooth/host/privacy/central compile
60 app=tests/bsim/bluetooth/host/privacy/peripheral compile
61 app=tests/bsim/bluetooth/host/privacy/device compile
/Zephyr-Core-3.4.0/samples/bluetooth/direct_adv/
DREADME.rst23 * Second BLE device acting as a central with enabled privacy. For example another Zephyr board
/Zephyr-Core-3.4.0/subsys/bluetooth/mesh/
Dsubnet.h34 uint8_t privacy[16]; /* PrivacyKey */ member
Dsolicitation.c156 err = bt_mesh_net_obfuscate(out->data, 0, sub->keys[i].msg.privacy); in sol_pdu_decrypt()
316 sub->keys[SUBNET_KEY_TX_IDX(sub)].msg.privacy); in sol_pdu_create()
Dsubnet.c284 return bt_mesh_k2(key, p, p_len, &cred->nid, cred->enc, cred->privacy); in msg_cred_create()
302 LOG_DBG("PrivacyKey %s", bt_hex(keys->msg.privacy, 16)); in net_keys_create()
Dnet.c488 return bt_mesh_net_obfuscate(buf->data, iv_index, cred->privacy); in net_encrypt()
640 cred->privacy)) { in net_decrypt()
Dfriend.c522 if (bt_mesh_net_obfuscate(buf->data, iv_index, cred->privacy)) { in encrypt_friend_pdu()
DKconfig1625 build as it compromises the privacy of the device.
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/api/mesh/
Dpriv_beacon_cli.rst14 The Private Beacons feature adds privacy to the different Bluetooth mesh
Dpriv_beacon_srv.rst14 The Private Beacons feature adds privacy to the different Bluetooth mesh
Dproxy.rst24 privacy of the network.
/Zephyr-Core-3.4.0/subsys/bluetooth/host/
DKconfig368 bool "Device privacy"
370 Enable privacy for the local device. This makes the device use Resolvable
375 advertiser is only possible if the controller also supports privacy.
390 This option increases privacy, as explained in the following text.
409 For optimal privacy, a new IRK (i.e., identity) should be used per
/Zephyr-Core-3.4.0/doc/releases/
Drelease-notes-2.0.rst438 * Nordic: Added support for Controller-based privacy, fast encryption
686 …`18306` - Unable to reconnect paired devices with controller privacy disabled (host privacy enable…
727 * :github:`18048` - [zephyr 1.14] Zephyr with privacy does not disconnect device with unresolvable …
741 * :github:`17979` - Security level cannot be elevated after re-connection with privacy
749 * :github:`17948` - Bluetooth: privacy: Reconnection issue
762 * :github:`17880` - Unable to re-connect to privacy enabled peer when using stack generated Identity
777 …ub:`17802` - [zephyr 1.14] Address type 0x02 is used by LE Create Connection in device privacy mode
949 * :github:`16893` - Bluetooth: Multiple local IDs, privacy problem
1336 * :github:`14675` - Bluetooth: Controller privacy support (platforms with HW acceleration)
Drelease-notes-1.14.rst157 * :github:`16893` - Bluetooth: Multiple local IDs, privacy problem
192 …ub:`17802` - [zephyr 1.14] Address type 0x02 is used by LE Create Connection in device privacy mode
198 * :github:`17880` - Unable to re-connect to privacy enabled peer when using stack generated Identity
200 * :github:`17948` - Bluetooth: privacy: Reconnection issue
203 * :github:`17979` - Security level cannot be elevated after re-connection with privacy
209 …`18306` - Unable to reconnect paired devices with controller privacy disabled (host privacy enable…
356 * :github:`16893` - Bluetooth: Multiple local IDs, privacy problem
391 …ub:`17802` - [zephyr 1.14] Address type 0x02 is used by LE Create Connection in device privacy mode
398 * :github:`17880` - Unable to re-connect to privacy enabled peer when using stack generated Identity
404 * :github:`17948` - Bluetooth: privacy: Reconnection issue
[all …]
Drelease-notes-1.9.rst144 * Controller-based privacy (including all optional features)
Drelease-notes-2.3.rst320 - Enabled controller-based privacy
643 * Controller-based privacy support.
1196 * :github:`23222` - Bluetooth: host: Unable to pair when privacy feature is disabled by application
Drelease-notes-2.1.rst537 * :github:`20620` - Advertiser seen alternating between RPA an ID address with privacy enabled
707 * :github:`19509` - Bluetooth: stm32wb55: Unable to pair with privacy-enabled peer
Drelease-notes-1.12.rst219 privacy
291 * :github:`1620` - BT 4.2 Controller-based link-layer privacy
Drelease-notes-2.2.rst635 * Implemented software-deferred privacy for platforms without built-in
1218 * :github:`9349` - Support IPv6 privacy extension RFC 4941
Drelease-notes-1.10.rst246 * :github:`1629` - LE privacy 1.2
Drelease-notes-2.5.rst717 * When privacy has been enabled in order to advertise towards a
718 privacy-enabled peer the BT_LE_ADV_OPT_DIR_ADDR_RPA option must now
719 be set, same as when privacy has been disabled.
Drelease-notes-3.3.rst2827 - :github:`54770` - Bluetooth: GATT: CCC and CF values written by privacy-disabled peer before bond…
2856 * :github:`54770` - Bluetooth: GATT: CCC and CF values written by privacy-disabled peer before bond…
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/
Dbluetooth-shell.rst207 privacy-enabled and supports address resolution of the target address in directed advertisement.
/Zephyr-Core-3.4.0/subsys/bluetooth/controller/
DKconfig.ll_sw_split148 Enable support for software based deferred privacy calculations.

12