Finish side-porting commits from mbedtls-restricted that missed the split #318
No reviewers
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!318
Loading…
Reference in a new issue
No description provided.
Delete branch "prr_573-remainder-crypto"
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?
When we split Mbed Crypto from Mbed TLS, we missed the last few commits in the restricted branch of Mbed TLS which were quarantined security fixes. These commits are present in the git history of Mbed TLS, but their effect was cancelled by the removal of crypto files, and the commits never appeared in Mbed Crypto.
We're fixing this through 3 pull requests:
pk.h, cherry-picked here forrsa.h.config-suite-b.h(throughtest-ref-configs.pl), provide the desired coverage, namely having some test fail if the maximum signature size is not calculated correctly, especially in a configuration where RSA is disabled and the smallest MPI is just large enough for ECC.(
#rNNNare private links.)This pull request deliberately omits the addition of a run of
programs/pkey/pk_signtoall.sh. While this would be desirable, it wasn't in scope of #r573, and was only added there as a non-regression test which is now performed through unit tests. A better approach to smoke-test sample programs would be through demo scripts as in https://github.com/ARMmbed/mbedtls/pull/2698.Goal of this PR: all the commits that had gone missing are now present in Mbed Crypto.
Internal ref: IOTCRYPT-969