| commit | 141472c21a99f88f8911b6783302eee10aec9a82 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Oct 16 01:54:58 2021 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Oct 18 16:18:25 2021 +0000 |
| tree | 4eed5daf15d52a15f1b34f3f97860a274cfaa924 | |
| parent | 7c1f40f2f8fd04f4595be47b3a676d6587dd2943 [diff] |
Document some more ASN1_ITEM-associated functions. In doing so, fix ASN1_item_pack to not use the ASN1_OCTET_STRING typedef. The function makes an untyped ASN1_STRING. With all these caveats, one might think that ASN1_BOOLEAN ASN1_ITEMs are pretty useless. This is about right. They're really only usable embedded as a field in another struct. Bug: 426 Change-Id: Id7830b91b2d011038ce79ec848e17ad6241423e1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/49926 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: