| commit | 298d8bea0356799ce77c871b22fd6780383365bf | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Aug 24 16:54:35 2020 -0400 |
| committer | Adam Langley <agl@google.com> | Wed Aug 26 17:32:15 2020 +0000 |
| tree | b9456c5c97f4c52e5dc1ecde1aa7142f04d32828 | |
| parent | 1c58648f14ed75f2a8cc3ae08897987d97f493ec [diff] |
Add subject key ID and authority key ID accessors. Although extensions are accessible via X509_get_ext_d2i, OpenSSL's X509 object carries caches of a number of extensions. OpenSSL added accessors for some of these in 1.1.0 (X509_get0_subject_key_id) and 1.1.1d (the others), so mirror this. Note that, although they look like simpler getters, the error-handling is tricky. (For now I'm just looking to mirror OpenSSL's accessors and finally make the structs opaque. Go's x509.Certificate structure also recognizes a collection of built-in certificate fields, but error-handling is in the parser. That could be one path out of this cached fields mess, at the cost of making the parse operation do more work.) Change-Id: I051512aa296bd103229ba6eb2b5639d79e9eb63f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42624 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: