Skip to content

Conversation

@m-alperen-sener
Copy link
Contributor

Cherry-pick for deprecating fixed passkey.

* 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should I do it here? I don't know actually since this is upstream commit? any suggestion?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is better to fix this in upstream instead of noup here.

@m-alperen-sener m-alperen-sener force-pushed the fixed_passkey_derecation branch 4 times, most recently from 58f2d00 to aa4b946 Compare November 13, 2025 13:24
valeriosetti and others added 4 commits November 13, 2025 15:22
Remove previous Kconfig choices CONFIG_BT_MESH_USES_MBEDTLS_PSA and
CONFIG_BT_MESH_USES_TFM_PSA and use CONFIG_PSA_CRYPTO instead.
This commit also updates test code accordingly.

Signed-off-by: Valerio Setti <[email protected]>
(cherry picked from commit 019e26a)
Signed-off-by: alperen sener <[email protected]>
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]>
@m-alperen-sener m-alperen-sener force-pushed the fixed_passkey_derecation branch 2 times, most recently from 5bf5dc8 to 604af05 Compare November 13, 2025 14:37
…NFIG_PSA_CRYPTO"

This reverts commit 179f7f9.

Signed-off-by: alperen sener <[email protected]>
@m-alperen-sener m-alperen-sener force-pushed the fixed_passkey_derecation branch from 604af05 to 800163b Compare November 13, 2025 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants