Home
last modified time | relevance | path

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

12

/Zephyr-latest/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-latest/tests/bsim/bluetooth/
Dtests.nrf5340bsim_nrf5340_cpunet.txt13 tests/bsim/bluetooth/host/privacy/central
/Zephyr-latest/samples/bluetooth/direct_adv/
DREADME.rst24 * Second Bluetooth LE device acting as a central with enabled privacy. For example another Zephyr b…
/Zephyr-latest/subsys/bluetooth/mesh/
Dsubnet.h36 struct bt_mesh_key privacy; /* PrivacyKey */ member
Dproxy_srv.c66 bool privacy; member
327 err = bt_mesh_beacon_create(sub, &buf, client->privacy); in beacon_send()
1135 client->privacy = false; in gatt_connected()
1137 client->privacy = (bt_mesh_priv_gatt_proxy_get() == BT_MESH_FEATURE_ENABLED) || in gatt_connected()
1141 LOG_DBG("privacy: %d", client->privacy); in gatt_connected()
Dsolicitation.c155 err = bt_mesh_net_obfuscate(out->data, 0, &sub->keys[i].msg.privacy); in sol_pdu_decrypt()
319 &sub->keys[SUBNET_KEY_TX_IDX(sub)].msg.privacy); in sol_pdu_create()
Dsubnet.c201 bt_mesh_key_destroy(&key->msg.privacy); in subnet_keys_destroy()
304 return bt_mesh_k2(key, p, p_len, &cred->nid, &cred->enc, &cred->privacy); in msg_cred_create()
328 LOG_DBG("PrivacyKey %s", bt_hex(&keys->msg.privacy, sizeof(struct bt_mesh_key))); in net_keys_create()
508 bt_mesh_key_destroy(&cred->privacy); in bt_mesh_friend_cred_destroy()
Dnet.c489 return bt_mesh_net_obfuscate(buf->data, iv_index, &cred->privacy); in net_encrypt()
641 &cred->privacy)) { in net_decrypt()
Dfriend.c533 if (bt_mesh_net_obfuscate(buf->data, iv_index, &cred->privacy)) { in encrypt_friend_pdu()
/Zephyr-latest/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.rst23 privacy of the network.
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv6198 The stable IID enhances privacy by having a different IID for each
223 sacrificing the security and privacy of users.
238 This enables IPv6 privacy extension (RFC 8981) support.
255 privacy extension support according to this filter list.
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dtest_proxy_sol.c171 &sub->keys[SUBNET_KEY_TX_IDX(sub)].msg.privacy)); in sol_fixed_pdu_create()
/Zephyr-latest/subsys/bluetooth/host/
DKconfig445 bool "Device privacy"
447 Enable privacy for the local device. This makes the device use Resolvable
452 advertiser is only possible if the controller also supports privacy.
467 This option increases privacy, as explained in the following text.
486 For optimal privacy, a new IRK (i.e., identity) should be used per
854 If privacy is disabled, the scanner will use its identity
/Zephyr-latest/
DCODE_OF_CONDUCT.md71 All community leaders are obligated to respect the privacy and security of the
/Zephyr-latest/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-1.12.rst219 privacy
291 * :github:`1620` - BT 4.2 Controller-based link-layer privacy
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-4.1.rst580 * :dtcompatible:`intel,adsp-mic-privacy`
/Zephyr-latest/dts/xtensa/intel/
Dintel_adsp_ace30_ptl.dtsi450 compatible = "intel,adsp-mic-privacy";
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/
Dgap.rst171 privacy-enabled and supports address resolution of the target address in directed advertisement.

12