e5b6c141a1
All the C accesses have been sufficiently abstracted that this is pretty easy to handle automatically. We still have accesses from assembly, so we're not quite initializationless yet. But this does get us most of the way there. I'm thinking what's next is: - Make a list of asm symbols that touch armcap or ia32cap - For each, figure out the place(s) in the calling code where we need to init manually and/or pull the dispatch up into C One interesting subtlety with how this CL does it: although this CL means you can freely call, say, CRYPTO_is_SSSE3_capable without CRYPTO_library_init, you cannot *quite* assume that CRYPTO_library_init has been called after you call CRYPTO_is_SSSE3_capable. It is possible that the build defined __SSSE3__, in which case CRYPTO_is_SSSE3_capable does nothing. This does complicate resolving the asm cases above. Bug: 35 Change-Id: Ie52c74e4a59a7019c3af0526dbb35950604ada66 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62585 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@google.com>
BoringSSL
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
Project links:
There are other files in this directory which might be helpful:
- PORTING.md: how to port OpenSSL-using code to BoringSSL.
- BUILDING.md: how to build BoringSSL
- INCORPORATING.md: how to incorporate BoringSSL into a project.
- API-CONVENTIONS.md: general API conventions for BoringSSL consumers and developers.
- STYLE.md: rules and guidelines for coding style.
- include/openssl: public headers with API documentation in comments. Also available online.
- FUZZING.md: information about fuzzing BoringSSL.
- CONTRIBUTING.md: how to contribute to BoringSSL.
- BREAKING-CHANGES.md: notes on potentially-breaking changes.
- SANDBOXING.md: notes on using BoringSSL in a sandboxed environment.