|author||David Benjamin <email@example.com>||Thu Oct 06 15:07:20 2022 -0400|
|committer||Boringssl LUCI CQ <firstname.lastname@example.org>||Thu Oct 06 19:32:27 2022 +0000|
Add CBB_add_asn1_[u]int64_with_tag. CBB_add_asn1_uint64 doesn't work if you're encoding an implicitly-tagged INTEGER. Take a leaf from Go cryptobyte and add a "with tag" variant, rather than a "contents" variant, which is a little more convenient to use. It also avoids us having to decide how to name the contents field. Change-Id: I6072e55017230c513577c44c5a7ed86e778255b3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54685 Reviewed-by: Bob Beck <email@example.com> Commit-Queue: Bob Beck <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.com> Auto-Submit: David Benjamin <firstname.lastname@example.org>
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: