mirror of
https://github.com/yuzu-emu/mbedtls.git
synced 2024-11-23 03:05:43 +01:00
b99bd39b4e
Merge `unremove-non-crypto` into `mbedtls/development`. The branch `unremove-non-crypto` was obtained by starting from `mbed-crypto/development`, then reverting many commits that removed X.509 and TLS functionality when Mbed Crypto forked from Mbed TLS (the “unremoval”), then make a few tweaks to facilitate the merge. The unremoval step restored old versions of some tls files. If a file doesn't exist in mbed-crypto, check out the mbedtls version, regardless of what happened during the unremoval of tls files in the crypto tree. Also unconditionally take the mbedtls version of a few files where the modifications are completely project-specific and are not relevant in mbed-crypto: * `.github/issue_template.md`: completely different. We may want to reconcile them independently as a follow-up. * `.travis.yml`: would only be reverted to an earlier tls version. * `README.md`: completely different. We may want to reconcile them independently as a follow-up. * `doxygen/input/doc_mainpage.h`: the changes in crypto were minimal and not relevant except as a stopgap as mbed-crypto did not have its own product versioning in the Doxygen documentation. * `tests/.jenkins/Jenkinsfile`: completely different. * `tests/data_files/Makefile`: there were no changes in mbed-crypto, but the unremoval step restored an old version. Shell script for everything to do after the merge apart from the conflict resolution: ``` tls_files=($(comm -23 <(git ls-tree -r --name-only HEAD) <(git ls-tree -r --name-only $(git merge-base upstream-crypto/development MERGE_HEAD)))) tls_files+=($tls_files .github/issue_template.md .travis.yml README.md doxygen/input/doc_mainpage.h tests/.jenkins/Jenkinsfile tests/data_files/Makefile) git checkout --theirs HEAD -- $tls_files git add -- $tls_files ``` Resolve the remaining conflicts: * `library/CMakeLists.txt`: * Keep the TLS definition of `src_crypto` * `USE_SHARED_MBEDTLS_LIBRARY`: keep all three libraries, with both `include` and `crypto/include` in `target_include_directories`, all with version `2.21.0`. * `programs/Makefile`: * Reconcile the APPS lists (add/add from a differently-formatted common ancestor): insert the `psa/*` from crypto into the tls list. * Keep the `fuzz` target defined only in tls version. * Keep the recipe (only in tls version) cleaning `ssl_pthread_server` stuff for the `clean` target. * `scripts/config.py`: * `include_in_full`: add/add conflict. Keep both. * `tests/scripts/all.sh`: * `component_test_no_use_psa_crypto_full_cmake_asan`: partially old version in crypto. Take the tls version. * `component_test_malloc_0_null` and more: take `component_test_malloc_0_null` from crypto (with `config.py` rather than `config.pl`, and with `$ASAN_FLAGS` rather than an explicit list), but add the call to `ssl-opt.sh` from tls. Take the other components from crypto. With this commit, building and running the unit tests with both `make ` and `cmake` work in the default configuration on Linux. Other platforms, build systems and configurations are likely not to work, and there is some regression in test coverage. There is some loss of functionality because the unremoval step restored older versions of tls content. This commit contains the latest tls version of tls-only files, but some changes from the tls side in files that existed on both sides have regressed. Most problematic changes are hunks that remove some tls-specific feature and contain either a C preprocessor symbol identifying a tls-specific module or option, or the name of a tls-specific file. Hunks that remove a tls-specific preprocessor symbol can be identified with the regular expression `^-.*MBEDTLS_(ERR_)?(PKCS11|X509|NET|SSL)_`. Subsequent commits will revert a few parts of the patch from this merge commit in order to restore the tls functionality that it removes, ensure that the test coverage includes what was covered in either branch, and fix test failures. |
||
---|---|---|
.. | ||
mbedtls | ||
psa | ||
.gitignore | ||
CMakeLists.txt |