Bluetooth: Kconfig: Enable TINYCRYPT_ECC for combined builds
Essentially all products that support pairing or Mesh need to be able to support ECC. This is particularly important for traditional peripheral/central use cases where legacy pairing is considered insecure. With split builds we don't know if the controller supports ECC HCI commands or not, however with a combined build we know that the current controller lacks any special ECC support, so enable TINYCRYPT_ECC by default for such a configuration. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
c761002e30
commit
db0e4d5267
1 changed files with 4 additions and 1 deletions
|
@ -368,6 +368,7 @@ config BT_TINYCRYPT_ECC
|
|||
select TINYCRYPT
|
||||
select TINYCRYPT_ECC_DH
|
||||
depends on BT_HCI_RAW || BT_HCI_HOST
|
||||
default y if BT_CTLR && (BT_SMP || BT_MESH_PROV)
|
||||
help
|
||||
If this option is set TinyCrypt library is used for emulating the
|
||||
ECDH HCI commands and events needed by e.g. LE Secure Connections.
|
||||
|
@ -376,7 +377,9 @@ config BT_TINYCRYPT_ECC
|
|||
commands the LE Secure Connections support will be disabled.
|
||||
In builds including the HCI Raw interface and the BLE Controller, this
|
||||
option injects support for the 2 HCI commands required for LE Secure
|
||||
Connections so that Hosts can make use of those.
|
||||
Connections so that Hosts can make use of those. The option defaults
|
||||
to enabled for a combined build with Zephyr's own controller, since it
|
||||
does not have any special ECC support itself (at least not currently).
|
||||
|
||||
if BT_DEBUG
|
||||
config BT_DEBUG_SETTINGS
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue