Merge development-psa from mbedTLS into development #42
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!42
Loading…
Reference in a new issue
No description provided.
Delete branch "development-merged-dev-psa-409fdae"
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?
This PR supersedes https://github.com/ARMmbed/mbed-crypto/pull/40.
It merges development_psa from mbedtls repository (commit
409fdae) into development.The aim is to have a sibling PR to the big merge happening here: https://github.com/ARMmbed/mbedtls/pull/2395 , to have the tests pass on the TLS side. Then, an updated PR with development -> mbed-crypto merge will be created.
I have performed the following tests:
make test(passed);ssl-opt.sh(passed).Following conflicts have been resolved:
Manual changes:
I've performed a merge of development into this PR (without conflicts) to include Hanno's changes to public key format adaption code.
I've merged the https://github.com/ARMmbed/mbedtls/pull/2395 branch into the branch used in this PR, to have the tests passing on MbedTLS side.
Jaeden has created #51 which supersedes this.
Pull request closed