Update Mbed Crypto with latest Mbed TLS changes as of 2019-11-15 #322
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!322
Loading…
Reference in a new issue
No description provided.
Delete branch "merge-crypto-development-20191115"
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?
The previous update was https://github.com/ARMmbed/mbed-crypto/pull/223. Salient changes:
config.py, in particular withMBEDTLS_MEMORY_BUFFER_ALLOC_Cdisabled inconfig.py full.This is a merge commit (
9afbfdc833) and its follow-up.CI passed and produced the expected outcome file.
Internal ref: IOTCRYPT-974
Having gone through the merge myself, the conflict resolution looks correct to me, approving.
I did the merge myself and ran into a few meaningful differences, listed below. I ran into other differences as well, but those are stylistic and I don't mind going with another style.
None of these are blockers.
The diffs are
-for your PR version, and+for my merge./Sinprograms/Makefile. This provides consistency with what came before in the crypto branch, as/Swas already present there. No TLS branch removes/Sintentionally, so we shouldn't remove/Sfrom Crypto by this merge.component_test_no_use_psa_crypto_full_cmake_asan()inall.sh, I aligned with TLS by unsettingMBEDTLS_PSA_CRYPTO_C. We shouldn't make this test test more different configurations than it currently does: the merge should align the configuration used by this test where applicable.Given approving reviews and no blocking issues, merging. We can further align the TLS and Crypto branches as desired in follow up PRs.