|author||David Benjamin <email@example.com>||Tue Apr 28 17:13:27 2020 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri May 01 18:16:12 2020 +0000|
Move serialization of points inside pmbtoken.c. This reduces the number of places that know about the group and allows us to abstract between different PMBTokens variations. Although the abstraction isn't quite clean with the key_id in the TRUST_TOKEN serialization, so we may need to ponder this. Change-Id: Ia892340057025794aaf7c44a64c4d195a969715f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41065 Commit-Queue: Steven Valdez <firstname.lastname@example.org> Reviewed-by: Steven Valdez <email@example.com>
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.
There are other files in this directory which might be helpful: