boot/bootutil: add the option to use custom definitions for all crypto inline functions #1870
Conversation
This file contains 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
…ons instead of the prepared ones as previously discussed in mcu-tools#1478 Signed-off-by: Oliver Mueller <olstyle@gmx.de>
Olstyle
changed the title
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.
As previously discussed in #1478 , this adds a define named
MCUBOOT_USE_CUSTOM_CRYPT.Using that define,
headername_custom.hwill be included in the crypto headers instead of enabling any pre defined code path.Since the include calls throughout mcuboot are clean already, it is actually enough to implement only the used algorithms. So if e.g. RSA is not used, a definition of
rsa_custom.his NOT necessary.