Update c-utility to pick up mbedTLS 4.x support - #142
Merged
Ewerton Scaboro da Silva (ewertons) merged 1 commit intoAug 25, 2026
Conversation
mbedTLS 3.6 LTS goes EOL in March 2027. mbedTLS 4.0 removed the public entropy/CTR_DRBG modules, mbedtls_ssl_conf_rng() and mbedtls_ssl_conf_min_version(), and requires psa_crypto_init() before any cryptographic operation. c-utility's mbedTLS adapters guard those call sites on MBEDTLS_VERSION_NUMBER. Points at azure-c-shared-utility master (262123bc), the merge commit of Azure/azure-c-shared-utility#681. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Ewerton Scaboro da Silva (ewertons)
force-pushed
the
ewertons/mbedtls-4x-support
branch
from
August 24, 2026 20:07
e55d16a to
16b16bd
Compare
Ewerton Scaboro da Silva (ewertons)
added a commit
to Azure/azure-iot-sdk-c
that referenced
this pull request
Aug 24, 2026
mbedTLS 3.6 LTS goes EOL in March 2027 and mbedTLS 4.x is now the supported line. Rolls every azure-c-shared-utility reference forward to the commit carrying the mbedTLS 4.x adapter support, following the shape of #2662 which added mbedTLS 3.x support. The submodule consistency check requires all five references to the same repository to agree, so the four dependencies that embed c-utility are bumped together with the direct reference: c-utility -> azure-c-shared-utility master (262123bc) uamqp (deps/azure-c-shared-utility) umqtt (deps/c-utility) deps/uhttp (deps/c-utility) provisioning_client/deps/utpm (deps/c-utility) c-utility points at merged master. The four dependency pointers are still branch commits pending Azure/azure-uamqp-c#482, Azure/azure-umqtt-c#176, Azure/azure-uhttp-c#142 and Azure/azure-utpm-c#137; each must be re-pointed at its merged master commit before this is merged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
Re-pointed at azure-c-shared-utility master — Azure/azure-c-shared-utility#681 merged as Ready to come out of draft once CI confirms. |
Ewerton Scaboro da Silva (ewertons)
marked this pull request as ready for review
August 24, 2026 21:56
Avishek (avishekpant)
approved these changes
Aug 25, 2026
Ewerton Scaboro da Silva (ewertons)
deleted the
ewertons/mbedtls-4x-support
branch
August 25, 2026 20:40
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Updates the
azure-c-shared-utilitysubmodule to the commit adding mbedTLS 4.x support.mbedTLS 3.6 LTS reaches end of life in March 2027. mbedTLS 4.0 moved cryptography into TF-PSA-Crypto and removed the public entropy/CTR_DRBG modules,
mbedtls_ssl_conf_rng()andmbedtls_ssl_conf_min_version(), dropped thef_rng/p_rngparameters ofmbedtls_pk_parse_key(), madembedtls_pk_get_type()private, and requirespsa_crypto_init()before any cryptographic operation. The adapter fix is Azure/azure-c-shared-utility#681.Submodule pointer only; no source changes here.
azure-iot-sdk-creferencesazure-c-shared-utilityin five places and its consistency check requires them to agree, so this repo moves in lockstep with the others.