Add MbedTLS signature verification#54
Open
mzella-ll wants to merge 1 commit into
Open
Conversation
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.
Summary
This PR adds an MbedTLS-based implementation of
signature_verify().The existing OpenSSL implementation remains unchanged. When
MBEDTLSis defined, the function now performs real ECDSA signature verification instead of falling back to the temporary stub.Changes
randsvalues.signature_verify().secp256r1ECDSA curve.Motivation
Some embedded targets use MbedTLS instead of OpenSSL. These targets should be able to perform signature verification without depending on OpenSSL.
This change adds the missing MbedTLS verification backend while preserving the existing OpenSSL path.
Expected behavior
When built with
MBEDTLSdefined,signature_verify()verifies the provided ECDSA signature using MbedTLS.When built with
OPENSSLdefined, the existing OpenSSL implementation is used.When neither backend is enabled, the existing fallback behavior remains unchanged.
Related issue
Fixes #53