Start expanding and documenting PEM_read and PEM_write functions Like asn1.h and x509.h, this starts the process of expanding the functions hidden inside macros so that we can document them properly. To capture the many common conventions, have a sample block (matching what we did for asn1.h). I've done a handful of types to start with, so we can settle on the pattern to use. I'm thinking we'll start with these sections, put all the type-specific ones there, and then have a "Low-level functions" or "Reading and writing raw PEM blocks" or whatever for the rest. Bug: 42290574 Change-Id: I50fce8d4433c7fc676b5d187a518f23a25bdac17 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/97227 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: