Update to BearSSL 0.6+ release, add AES_CCM modes #5164
Merged
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
Pull in latest BearSSL head (0.6 + minor additions) release and add AES_CCM modes to the encryption options.
earlephilhower
force-pushed
the
bssl0.6updt
branch
from
31e4be5
to
12e666e
Compare
|
Are there flashsize or heap use implications here? |
|
There should be no real heap difference. There is going to be a slight code increase as these new codes will be included in the library. If flash size becomes an issue I can move from |
|
I observed that -Os can run faster than -O2 with other CPUs too (the gameboy advance's one arm7tdmi I believe it was) |
The EC mul20 and square20 code was identical in two different files, but because these copies were static, we ended up with an extra 6k of duplicated code. Updated BearSSL to make them shared, saving 6KB.
|
Tests with the latest update show <2KB flash growth on the BearSSL_Validation example. |
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.
Pull in latest BearSSL head (0.6 + minor additions) release and add AES_CCM
modes to the encryption options.