You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lib: peer_manager: associate peer_id after repairing check if dup bond
If duplicate bonding data is found in auth_status_success_process(),
first check if repairing is allowed before associating the peer_id with
the connection handle. If repairing is not allowed, then the
peer_id should not be associated with the connection handle.
Signed-off-by: Andreas Moltumyr <andreas.moltumyr@nordicsemi.no>
Copy file name to clipboardExpand all lines: doc/nrf-bm/release_notes/release_notes_changelog.rst
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,6 +143,8 @@ Libraries
143
143
* The LESC key agreement handling to clear the static RAM copy of the ECDH shared secret after the secret have been handed over to the SoftDevice using the :c:func:`sd_ble_gap_lesc_dhkey_reply` function.
144
144
* The :kconfig:option:`CONFIG_PM_LESC_GENERATE_NEW_KEYS` Kconfig option to be enabled by default.
145
145
This option forces the use of new ECDH key pair for each pairing procedure.
146
+
* The sources of the :c:enumerator:`PM_EVT_CONN_SEC_CONFIG_REQ` event to fill the peer ID field.
147
+
The value of the peer ID field should be used instead of calling the :c:func:`pm_peer_id_get` function when handling this event.
0 commit comments