f6d6742ca1
Added a Kconfig option that makes the RPA sharing feature optional. By default, the Zephyr Bluetooth stack now uses the RPA rotation policy that was active before the introduction of the RPA sharing functionality in the following PR: https://github.com/zephyrproject-rtos/zephyr/pull/55449 The new Kconfig option configures the advertising sets linked with the same Bluetooth identity to use the same Resolvable Private Address in a given rotation period. After the RPA timeout, the new RPA is generated and shared between the advertising sets in the subsequent rotation period. When this option is disabled, the generated RPAs of the advertising sets differ from each other in a given rotation period. Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| buf | ||
| crypto | ||
| data/bt_data_parse | ||
| ecc | ||
| host_mocks | ||
| id | ||
| keys | ||
| CMakeLists.txt | ||