| commit | 75148d7abf12bdd1797fec3c5da9a21963703516 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Nov 20 11:33:35 2019 +0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Nov 20 15:09:27 2019 +0000 |
| tree | 7b9531de104b8a184d8164345c7b869b14452ed3 | |
| parent | 6ba98ff60144f60aba589b4d6121689528fbae76 [diff] |
Halve the size of the kNIDsIn* constants We have not and are unlikely to ever allocate 65K NIDs, so these ables can use uint16_t and halve their size. Bug: 300 Change-Id: I5c69a366588f26df75b7b642bee6dd12ad8cc661 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38904 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.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.
Project links:
There are other files in this directory which might be helpful: