Improve robustness and testing of mbedtls_mpi_copy #346
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!346
Loading…
Reference in a new issue
No description provided.
Delete branch "mpi_copy_shrink"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Also improve testing of
mbedtls_mpi_swap.The robustness improvement could plausibly fix a bug in some applications, so this should be backported.
I checked the CI results, and the only failures are in Mbed OS testing, which is expected as Mbed OS needs updating, so it's as good as a pass.
For some reason the CI had directly reported failure without actually running any test. I'm restarting it.
I have two minor suggestions for improvement.
@ -292,37 +205,106 @@ mbedtls_mpi_cmp_abs:10:"2":10:"-3":-1Base test mbedtls_mpi_cmp_abs (Mix values) #3I am not sure I understand this description, could you please make it slightly more verbose?
@ -629,22 +604,40 @@ exit:/* END_CASE */Our existing tests are using big endian input and I think it would be less confusing to have consistency in this matter. Why do you prefer little endian by the way?
LGTM.
LGTM
Checked the CI and it only fails on Mbed OS with known issues that are unrelated to this PR.
The backport are now ready for merge, and so is this.