-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Deprecate BT_FIXED_APPKEY #25414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Deprecate BT_FIXED_APPKEY #25414
Conversation
Manifest update to depracate and replace BT_FIXED_PADDKEY Signed-off-by: alperen sener <[email protected]>
BT_FIXED_PASSKEY is depracated so wee need to aling the le pair responder model with the new Kconfig BT_APP_PASSKEY usage. Depracate bt_mesh_le_pair_resp_passkey_invalidate, it not needed anymore. Adding bt_mesh_le_pair_resp_passkey_get to be able to retreive the passkey set randomly or by app. Signed-off-by: alperen sener <[email protected]>
BT_FIXED_PASSKEY is deprecated, thus we start using BT_APP_PASSKEY Signed-off-by: alperen sener <[email protected]>
|
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 project with PR revision Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, click the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 29999998db0b2b74ff7e9edef8030e1a19d18fa6 more detailssdk-nrf:
zephyr:
Github labels
List of changed files detected by CI (14)Outputs:ToolchainVersion: cfa6b06338 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
|
You can find the documentation preview for this PR here. |
| endif # BT_MESH_DM_SRV | ||
|
|
||
| config BT_MESH_LE_PAIR_RESP | ||
| bool "LE Pairing Responder model" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| bool "LE Pairing Responder model" | |
| bool "LE Pairing Responder model [EXPERIMENTAL]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why 'Experimental'? Using this model allows fixed passkey to be not used by virtue of the architecture. Specification does not say that one should remove API or change APIs, the specification gives guideline that fixed passkey is not allowed. This model along with the underlaying API creates a system that make fulfilling this requirement possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because 2 lines down, you are selecting the EXPERIMENTAL Kconfig ?? https://github.com/nrfconnect/sdk-nrf/pull/25414/files#diff-6b6980f5c948cf835b4cfac2ecf56cb964fa0e31bd790325f3f17a351e23718dR90
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess, because it has experimental tag. Either we have to remove it or add what @nordicjm requested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, if you select EXPERIMENTAL then you should clearly mark it as experimental in the title, that is the convention
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll do that 👍
Deprecating BT_FIXED_PASSKEY and start using BT_APP_PASSKEY instead.