Fixed passkey deprecation #3466
Open
+157
−42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds the BT_APP_PASSKEY Kconfig, which allows the application to provide passkeys for pairing using the new `app_passkey()` callback. This is an alternative to BT_FIXED_PASSKEY, which will be deprecated in a later commit. Signed-off-by: Håvard Reierstad <[email protected]> (cherry picked from commit 6c64054) Signed-off-by: alperen sener <[email protected]>
The BT_FIXED_PASSKEY Kconfig option is being deprecated, and is replaced by BT_APP_PASSKEY. The reason for the deprecation is an upcoming errata, ES-24489, which mandates that a new passkey shall be generated for each pairing procedure. Signed-off-by: Håvard Reierstad <[email protected]> (cherry picked from commit 82cfb5a) Signed-off-by: alperen sener <[email protected]>
Updates the bt shell API to use the new Kconfig option BT_APP_PASSKEY instead of BT_FIXED_PASSKEY as this is being deprecated. Signed-off-by: Håvard Reierstad <[email protected]> (cherry picked from commit b6252b5) Signed-off-by: alperen sener <[email protected]>
This was referenced Nov 4, 2025
seko-nordic
reviewed
Nov 4, 2025
| * pairing, or BT_PASSKEY_RAND to generate a random passkey. This callback is invoked only | ||
| * for the Passkey Entry method as defined in Core Specification Vol. 3, Part H. Which | ||
| * device in the pairing is showing the passkey depends on the IO capabilities of the | ||
| * device; see Table 2.8 of the Bluetooth Core Specification V6.0, Vol. 3, Part H for more |
Contributor
There was a problem hiding this comment.
better not to specify version, so we don't need to update it with every spec release. The way core spec is developed guarantees that existing section numbers will not change in future specs.
Suggested change
| * device; see Table 2.8 of the Bluetooth Core Specification V6.0, Vol. 3, Part H for more | |
| * device; see Table 2.8 of the Bluetooth Core Specification, Vol. 3, Part H for more |
Contributor
Author
There was a problem hiding this comment.
should I do it here? I don't know actually since this is upstream commit? any suggestion?
Contributor
There was a problem hiding this comment.
It is better to fix this in upstream instead of noup here.
PavelVPV
approved these changes
Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick for deprecating fixed passkey.