nrf_security: add MBEDTLS_AES_ONLY_128_BIT_KEY_LENGTH option #15368
Conversation
LuDuda
requested review from
frkv,
Vge0rge,
vlilleboe,
SebastianBoe,
mswarowsky,
carlescufi and
tejlmand
as code owners
github-actions
bot
added
manifest
changelog-entry-required
|
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
LuDuda
force-pushed
the
pr/aes128
branch
2 times, most recently
from
30299cf to
2465e01
Compare
Memory footprint analysis revealed the following potential issuesapplications.nrf_desktop.zrelease_nrf54h20[nrf54h20dk/nrf54h20/cpuapp]: RAM size increased by 773[B] in comparison to the main[5df2bed] branch. - link (cc: @MarekPieta) Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-15368/4) |
This commit allows application to set mbedTLS option that allow to remove support for AES operations that use 192- or 256-bit keys. Signed-off-by: Łukasz Duda <lukasz.duda@nordicsemi.no>
This commit allows application to set mbedTLS option that allow to remove support for AES operations that use 192- or 256-bit keys.
It also enables it by default for Matter over Wi-Fi applications.