Repository navigation
Enable upstream arithmetic kernels for embedded TLS - #2
Merged
Merged
Conversation
JohnAmadis
approved these changes
Oct 17, 2026
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
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.
Enable upstream-default MBEDTLS_HAVE_ASM in the private crypto configuration, selecting architecture/compiler arithmetic kernels while retaining the portable fallback. Keep the host provider compatible with the new dmutc source DIF declarations so fresh, unversioned dependencies compile in CI.
Algorithms, supported group order, mandatory verification, public ABI, entropy/time requirements, SDK/loader and DMF format remain unchanged. Temporary tracing and experimental curve/window settings are absent from this change.
Validation: real-module native checks 3/3, OpenSSL interoperability 18/18, pointer-audit fixtures 3/3; native/M4/M7 builds and final-ELF audits pass. CI is green for all three profiles, including current dmutc headers. Through choco-technologies/dmhttp#1, STM32 verified Ethernet HTTPS passed 3/3 with reference body checks; a 64 KiB binary transfer and UTC/RTC/RNG regressions also passed.
Arithmetic optimization alone does not make every longer ECC-chain public-server attempt reliable. The observed latency/truncation issue is tracked in #3. Raw hardware logs stay local.