Skip to content

Commit 9ab733f

Browse files
MarekPietakapi-no
authored andcommitted
doc: migration: Add Bluetooth LE legacy pairing entry for NCS 3.0
Change adds a migration guide entry to improve visibility. Jira: NCSDK-35238 Signed-off-by: Marek Pieta <[email protected]>
1 parent 9f36cb0 commit 9ab733f

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

doc/nrf/releases_and_maturity/migration/migration_guide_3.0.rst

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,19 @@ ZMS settings backend
105105
To migrate from the legacy backend to the new backend remove the Kconfig options :kconfig:option:`CONFIG_SETTINGS_ZMS_NAME_CACHE`
106106
and :kconfig:option:`CONFIG_SETTINGS_ZMS_NAME_CACHE_SIZE` from your conf files.
107107

108+
Bluetooth LE legacy pairing
109+
---------------------------
110+
111+
.. toggle::
112+
113+
Support for Bluetooth LE legacy pairing is no longer enabled by default, because it is not secure.
114+
The :kconfig:option:`CONFIG_BT_SMP_SC_PAIR_ONLY` Kconfig option is enabled by default in Zephyr.
115+
If you still need to support the Bluetooth LE legacy pairing and you accept the security risks, disable the option in the configuration.
116+
117+
.. note::
118+
Using Bluetooth LE legacy pairing introduces, among others, a risk of passive eavesdropping.
119+
Supporting Bluetooth LE legacy pairing makes devices vulnerable to downgrade attacks.
120+
108121
nRF54H20
109122
========
110123

0 commit comments

Comments
 (0)