applications: nrf_desktop: Add a note about disabling BLE legacy pairing #20619
Conversation
github-actions
bot
added
the
doc-required
|
After documentation is built, you will find the preview for this PR here. Preview links for modified nRF Connect SDK documents: https://ncsdoc.z6.web.core.windows.net/PR-20619/nrf/app_dev/device_guides/nrf54l/kmu_provision.html |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 3950a1e0824599d4adf2996017f958aa8b102402 more detailssdk-nrf:
Github labels
List of changed files detected by CI (1)Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
MarekPieta
force-pushed
the
desktop_security_release_note
branch
from
519c4e9 to
13ec0fb
Compare
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
| @@ -254,6 +254,12 @@ nRF Desktop | |||
| This change results from the Bluetooth subsystem transition to the PSA cryptographic API. | |||
| The GATT database hash calculation now requires larger stack size. | |||
|
|
|||
| * Support for Bluetooth LE legacy pairing is no longer enabled by default, because it's not secure. | |||
| Using Bluetooth LE legacy pairing introduces risk of eavesdropping. | |||
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
Can we add it as an example (this one is relevant for BLE HID use-case I think):
Using Bluetooth LE legacy pairing introduces, among others, risk of eavesdropping.
|
You can find the documentation preview for this PR here. Preview links for modified nRF Connect SDK documents: |
MarekPieta
force-pushed
the
desktop_security_release_note
branch
from
4727183 to
af91234
Compare
| Using Bluetooth LE legacy pairing introduces, among others, a risk of eavesdropping. | ||
| Supporting Bluetooth LE legacy pairing makes devices vulnerable for a downgrade attack. |
There was a problem hiding this comment.
Could we combine these two and say, for example:
Bluetooth LE legacy pairing introduces, for example, a risk of eavesdropping and makes devices vulnerable for a downgrade attack.
Or is it different case for using and just supporting?
There was a problem hiding this comment.
I tried to separate the using from supporting here
Change introduces a release note to inform that BLE legacy pairing was disabled by default in application configurations. Jira: NCSDK-31809 Signed-off-by: Marek Pieta <[email protected]> Signed-off-by: Pekka Niskanen <[email protected]>
MarekPieta
force-pushed
the
desktop_security_release_note
branch
from
af91234 to
3950a1e
Compare
|
Change introduces a release note to inform that BLE legacy pairing was disabled by default in application configurations.
Jira: NCSDK-31809