|author||David Benjamin <firstname.lastname@example.org>||Fri Jun 19 17:58:27 2020 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Jun 23 17:57:25 2020 +0000|
Const-correct various functions in crypto/asn1. The const ASN1_TIME getters don't work well because some const functions aren't marked as such. I took a pass over the header and fixed the ones I noticed. Change-Id: I7eede530abc14ba0aab5763561c6f2dcf09e9659 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41824 Commit-Queue: David Benjamin <email@example.com> Reviewed-by: Adam Langley <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: