Repository navigation
Adapt TLS backend tables without changing the DMOD format - #1
Merged
Merged
Conversation
This was referenced Oct 16, 2026
Merged
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.
Adapt Mbed TLS 4.1.1 TLS/X.509 description tables for the existing DMOD GOT ABI. Under MBEDTLS_DMOD_C, constant descriptor strings are inline arrays and sentinel checks use numeric codes/lengths. Update the TF-PSA-Crypto submodule to the matching fork, which places callback and ECC references in DMOD_GLOBAL_POINTER slots and provides startup hooks. No cryptographic arithmetic or certificate verification rules are replaced.
This removes the need for the rejected DMOD relocation-table/file-format extension. Normal backend configurations retain upstream pointer fields; dmtls keeps the configured backend ABI private. The dmod/main baseline contains unchanged generated library sources from the official source release. See README-DMOD.md.
Validated through choco-technologies/dmtls#1: native real-module lifecycle 3/3, OpenSSL interoperability 18/18, STM32 TLS probes 7/7 followed by UTC 6/6, RTC 12/12 and RNG 6/6, using the unchanged DMOD loader. Build-time ELF auditing verifies that the existing GOT/header/API relocation paths suffice.