-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
modules: mbedtls: remove default-enabling of hash algorithms #72078
modules: mbedtls: remove default-enabling of hash algorithms #72078
Conversation
6e530fd
to
214abae
Compare
There are some tests failing in CI due some tangled build options, but I think that is the right direction. Features should be disabled by default and explicitly requested. |
214abae
to
d66f1b1
Compare
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. |
d66f1b1
to
ebb4f3d
Compare
Changes on Zephyr looks fine for me. Lets get modules in and update it. |
039169f
to
08602f8
Compare
Do not enable hash algorithms except SHA-256 by default. This unnecessarily inflates the final code size even if not all the enabled hash algorithms are actually used. SHA-256 is (for now) kept enabled by default because many configurations across the code base assume that there is some hash algorithm available without needing to enable it. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Explicitly enable SHA-512 now that it is not enabled by default anymore. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
08602f8
to
cb3ffae
Compare
This is ready for review. |
@tomi-font looks like some TLS tests started failing after this got merged https://github.com/zephyrproject-rtos/zephyr/runs/24575825044, could you look into it? |
Fix the failures introduced in zephyrproject-rtos#72078 by manually enabling all the hash algorithms as they used to be. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
@fabiobaltieri Thanks for the heads-up. I opened a fix PR: #72334 |
@tomi-font would this PR warrant a line in the migration guidelines? |
Yeah, actually I started thinking about this afterwards. It does seem like a good idea. There will be other related PRs and changes made to the configuration; I'll address this point in a follow-up PR. |
Fix the failures introduced in #72078 by manually enabling all the hash algorithms as they used to be. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
For changes brought by PRs zephyrproject-rtos#71118 and zephyrproject-rtos#72078. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
For changes brought by PRs zephyrproject-rtos#71118 and zephyrproject-rtos#72078. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
For changes brought by PRs zephyrproject-rtos#71118 and zephyrproject-rtos#72078. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Fix the failures introduced in zephyrproject-rtos#72078 by manually enabling all the hash algorithms as they used to be. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
For changes brought by PRs zephyrproject-rtos#71118 and zephyrproject-rtos#72078. Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Do not enable hash algorithms except SHA-256 by default.
This unnecessarily inflates the final code size even if not all the enabled hash algorithms are actually used.
SHA-256 is (for now) kept enabled by default because many configurations across the code base assume that there is some hash algorithm available without needing to enable it.
Relates to (and will help) #71947.