-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for BoringSSL CHIPCryptoPAL backend #20824
Conversation
- OpenSSL still works - Updated necessary differences - Added tests for Matter-compliant AES-CCM128 with 16 byte tag, 13 byte nonce - Added build files
PR #20824: Size comparison from 6185156 to b8971f6 Increases (2 builds for cc13x2_26x2, telink)
Decreases (1 build for cc13x2_26x2)
Full report (23 builds for bl602, cc13x2_26x2, cyw30739, k32w, linux, mbed, p6, telink)
|
PR #20824: Size comparison from 6185156 to b793585 Increases (2 builds for telink)
Decreases (12 builds for k32w, linux)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
This is great! Shouldn't everything in Also, are all the platform-specific assembly files Matter-specific or can those come in as submodule(s) too? |
I followed the conventions for src folder from the boringssl source generation script. We can clean-up the build more once we start using the asm. For now, those are generated from the repos at regular interval. |
PR #20824: Size comparison from cd4ab7c to 445ac4e Increases (4 builds for cc13x2_26x2, esp32, k32w)
Decreases (14 builds for cc13x2_26x2, linux, telink)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
PR project-chip#20824 moved some defines out of CryptoBuildConfig.h by mistake. This caused some defines to be globalized but only in GN builds. Fixes project-chip#20883 This PR brings back the defines in CryptoBuildConfig.h and fixes what's needed for that to build Testing done: - Unit tests still pass - Integration tests still pass
* Fix CryptoBuildConfig.h usage PR #20824 moved some defines out of CryptoBuildConfig.h by mistake. This caused some defines to be globalized but only in GN builds. Fixes #20883 This PR brings back the defines in CryptoBuildConfig.h and fixes what's needed for that to build Testing done: - Unit tests still pass - Integration tests still pass * Add BoringSSL coverage to rotating ID build
* Fix CryptoBuildConfig.h usage PR #20824 moved some defines out of CryptoBuildConfig.h by mistake. This caused some defines to be globalized but only in GN builds. Fixes #20883 This PR brings back the defines in CryptoBuildConfig.h and fixes what's needed for that to build Testing done: - Unit tests still pass - Integration tests still pass * Add BoringSSL coverage to rotating ID build
* Add boringssl submodule * Ran GN build generator from boringssl repos, added files * Boring SSL fully working - OpenSSL still works - Updated necessary differences - Added tests for Matter-compliant AES-CCM128 with 16 byte tag, 13 byte nonce - Added build files * Restyled * Fix CI, remove some forgotten remainders Co-authored-by: Tennessee Carmel-Veilleux <[email protected]>
* Fix CryptoBuildConfig.h usage PR #20824 moved some defines out of CryptoBuildConfig.h by mistake. This caused some defines to be globalized but only in GN builds. Fixes #20883 This PR brings back the defines in CryptoBuildConfig.h and fixes what's needed for that to build Testing done: - Unit tests still pass - Integration tests still pass * Add BoringSSL coverage to rotating ID build Co-authored-by: Tennessee Carmel-Veilleux <[email protected]>
Problem
Change overview
third_party/boringssl/repo/src
.third_party/boringssl/repo
are auto-generated by a builder script that copies the assembly versions by platform in a way that allows platform selection by GN later down the line (see https://github.com/google/boringssl/blob/master/util/generate_build_files.py)Testing